You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an SQL database dump will use COPY INTO syntax. This syntax is fast, but incompatible with loaders such as Java-based Ant sql task, because interfaces such as JDBC do not support the stream input switch necessary to perform the load of the COPY INTO.
It would therefore be nice when the dump could also be made using INSERT INTO statements, such that those tools can just process the dump. Additionally, this may ease migration of data to other databases.
implement bug #2727: allow using INSERT INTO statements in dump
INSERT INTO statements are more portable, and a necessity when using
loaders that have to adhere to a query & answer protocol, such as most
data source abstractions (most well known and standardised ones: ODBC
and JDBC).
Date: 2010-11-19 12:58:38 +0100
From: @grobian
To: clients devs <>
Version: -- development
Last updated: 2011-03-28 17:31:34 +0200
Comment 15212
Date: 2010-11-19 12:58:38 +0100
From: @grobian
Currently, an SQL database dump will use COPY INTO syntax. This syntax is fast, but incompatible with loaders such as Java-based Ant sql task, because interfaces such as JDBC do not support the stream input switch necessary to perform the load of the COPY INTO.
It would therefore be nice when the dump could also be made using INSERT INTO statements, such that those tools can just process the dump. Additionally, this may ease migration of data to other databases.
Comment 15309
Date: 2010-12-10 13:52:55 +0100
From: @grobian
Changeset 3375a722bb1e made by Fabian Groffen fabian@cwi.nl in the MonetDB repo, refers to this bug.
For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3375a722bb1e
Changeset description:
Comment 15310
Date: 2010-12-10 13:53:23 +0100
From: @grobian
Implemented.
Comment 15635
Date: 2011-03-28 17:31:34 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
The text was updated successfully, but these errors were encountered: