[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Fri Mar 4 00:11:04 -0800 2005 --- @justin: I submitted issue 44050 for discussion things which speaking strictly do no

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Thu Mar 3 07:50:27 -0800 2005 --- Heh Heh Heh Yeah, I know the feeling with this stuff. :) It's almost 3am here, and

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Thu Mar 3 06:43:40 -0800 2005 --- created via Tools|SQL in OOo :). Executed the following: CREATE TABLE customer ( c

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Thu Mar 3 06:00:34 -0800 2005 --- Thanks Frank. One thought: Was the table you're testing with created in OOo, or a t

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Thu Mar 3 05:10:49 -0800 2005 --- Hmm. With OOo 2.0 Beta Candidate (and also with the latest developer snapshots), I d

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Wed Mar 2 14:56:51 -0800 2005 --- Hi Joerg, Sure, but that only helps in a very small set of environments. + Produc

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Wed Mar 2 12:44:44 -0800 2005 --- Hi, just for the records, > it'd make PostgreSQL, Oracle, and possibly SQL > Serv

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Tue Mar 1 02:46:04 -0800 2005 --- Quick and dirty workaround thought... Would it be possible to check for error 24000

[dba-issues] [Issue 3872] Unable to use the serial (sequence) field from PostgreSQL

To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=3872 --- Additional comments from [EMAIL PROTECTED] Tue Mar 1 02:29:31 -0800 2005 --- Hi, Also, this is very similar (probably the same) error that occurs with Oracle 9i