title: DBeaver does not keep primary keys on import/export
body: <p>I'm using DBeaver to migrate data from Postgres to Derby.  When I use the wizard in DBeaver to go directly from one table to another, the primary key in Derby is being generated instead of inserted.  This causes issues on foreign keys for subsequent tables.</p>
  <p>If I generate the SQL, the primary key is part of the SQL statement and is properly inserted.  However there are too many rows to handle in this way.</p>
  <p>Is there a way to have DBeaver insert the primary key instead of letting it be generated when importing / exporting directly to database tables?</p>
  <p><strong>Schema of target table</strong></p>
  <pre class="lang-sql prettyprint-override"><code>CREATE TABLE APP.THREE_PHASE_MOTOR (
      ID BIGINT NOT NULL DEFAULT GENERATED_BY_DEFAULT,
      VERSION INTEGER NOT NULL,
      CONSTRAINT SQL130812103636700 PRIMARY KEY (ID)
  );
  
  CREATE INDEX SQL160416184259290 ON APP.THREE_PHASE_MOTOR (ID);
  </code></pre>
  <p><strong>Schema of source table</strong></p>
  <pre class="lang-sql prettyprint-override"><code>CREATE TABLE public.three_phase_motor (
      id int8 NOT NULL DEFAULT nextval('three_phase_motor_id_seq'::regclass),
      &quot;version&quot; int4 NOT NULL,
      CONSTRAINT three_phase_motor_pkey PRIMARY KEY (id)
  )
  WITH (
      OIDS=FALSE
  );
  </code></pre>