-
manningr changed the public information on the SQuirreL DB Copy Plugin project.
2009-08-29 12:00:41 UTC by manningr
-
manningr changed the public information on the SQuirreL DB Copy Plugin project.
2009-08-29 12:00:40 UTC by manningr
-
I'm using SQuirrel 3.0.1, DB2 9.5 and PosgreSQL 8.3
When I copy tables from DB2 to PostgreSQL, the "ON DELETE CASCADE" on foreign key constraints are not copied over. Instead, they become "ON DELETE NO ACTION".
2009-05-21 00:26:05 UTC by slhsien
-
When a copy to a H2 database occurs it creates this SQL "CREATE TABLE databasename.tablename.tablename" when it should create this
"CREATE TABLE databasename.schemaname.tablename". So fails everytime.
V 1.1.3 in SQuirreL SQL V 2.6.9.
2009-04-15 09:55:04 UTC by olddave
-
Hello,
I read this in the TODO.txt : "Right now, classname of the driver class is hard-linked to the Hibernate dialect class"
Could you please add a way to specify that link in a property file or something else ? It's quite a quick change but it can help us waiting for a best solution.
( btw, our problem is that the source database is RDB, so DBCopy doesn't find the dialect for RDB...
2009-02-11 14:12:35 UTC by bheurter
-
When I was copying Table to another database,
(MySQl to H2, 97 tables, off index option)
I suddenly executed some 'select SQL' in SQuirreL window, and found error message in SQuirreL log window saying.
Error: Streaming result set com.mysql.jdbc.RowDataDynamic@ac6782 is still active. No statements may be issued when any streaming result sets are open and in use on a given connection...
2008-07-29 06:22:51 UTC by rainywindow
-
Andreas,
With the new domain statement I was able to add support for this - only when copying from PostgreSQL. The underlying type is determined using pg's information_schema and then that type is used in the destination database. I'm not sure how portable user-defined types are at the moment, so I haven't attempted to re-create the domain in the destination database. The new SQuirreL snaps.
2008-06-03 09:40:24 UTC by manningr
-
Oops, sorry. The type "int_unsigned" is no new PostgreSQL data type.
It was defined with the following statement:
CREATE DOMAIN int_unsigned AS integer CONSTRAINT int_unsigned_check CHECK ((VALUE >= 0));
Sorry for any confusion caused.
Andreas.
2008-06-02 07:03:16 UTC by deining
-
Hmmm... I can't create these tables in PostgreSQL 8.2. The int_unsigned type doesn't exist:
Error: ERROR: type "int_unsigned" does not exist
SQLState: 42704
ErrorCode: 0
Is this a new 8.3 data type? I thought I would it at the link below, but it's not listed:
http://www.postgresql.org/docs/8.3/interactive/datatype.html
I'll setup 8.3 and try this again.
Rob.
2008-05-30 21:46:13 UTC by manningr
-
Thanks for the create table script - that will help me troubleshoot and possibly enable me to add support for the data types that are currently no supported. As far as the column name "count" that appears to be an invalid column name - that is probably a red herring. There is a setting that controls this "aggressive" column name checking that you can disable. What it attem.
2008-05-30 17:34:25 UTC by manningr
