On Sat, Oct 04, 2003 at 14:24:40 -0400,
Tom Lane [EMAIL PROTECTED] wrote:
Bruno Wolff III [EMAIL PROTECTED] writes:
The following is still a problem in current cvs (as of 2 hours ago).
Not any more ;-)
Thanks. I tried it out and it is now working for me.
---(end
The following is still a problem in current cvs (as of 2 hours ago).
Normally I wouldn't bug people about this again this soon, but with talk of
a release candidate next week I wanted to make sure that it wasn't forgotten.
On Sun, Sep 28, 2003 at 20:14:03 -0500,
Bruno Wolff III [EMAIL
When grilled further on (Sat, 4 Oct 2003 12:50:27 -0500),
Bruno Wolff III [EMAIL PROTECTED] confessed:
The following is still a problem in current cvs (as of 2 hours ago).
Normally I wouldn't bug people about this again this soon, but with talk of
a release candidate next week I wanted to make
I have added this to the 7.4 open items list:
Fix pg_dump of CREATE TABLE test (col1 BOOLEAN CONSTRAINT test
CHECK (col1))
---
Bruno Wolff III wrote:
The following is still a problem in current cvs (as of
Bruno Wolff III [EMAIL PROTECTED] writes:
The following is still a problem in current cvs (as of 2 hours ago).
Not any more ;-)
regards, tom lane
---(end of broadcast)---
TIP 9: the planner will ignore your desire to
Bruce Momjian [EMAIL PROTECTED] writes:
I have added this to the 7.4 open items list:
Fix pg_dump of CREATE TABLE test (col1 BOOLEAN CONSTRAINT test
CHECK (col1))
Fixed now.
regards, tom lane
---(end of
On Sun, Sep 28, 2003 at 23:16:48 -0400,
Bruce Momjian [EMAIL PROTECTED] wrote:
Christopher Kings-Lynne wrote:
If you are referring to my patch, Bruce - that does not fix it. Mine
only addresses psql.
I don't think that pg_dump uses pg_get_constraintdef(). It's probably a
side
Bruno Wolff III wrote:
On Sun, Sep 28, 2003 at 23:16:48 -0400,
Bruce Momjian [EMAIL PROTECTED] wrote:
Christopher Kings-Lynne wrote:
If you are referring to my patch, Bruce - that does not fix it. Mine
only addresses psql.
I don't think that pg_dump uses
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
If you are referring to my patch, Bruce - that does not fix it. Mine
only addresses psql.
It strikes me that maybe your patch should add parens always, rather
than just in the prettyprint case.
I don't think that pg_dump uses
If you have a check constraint that tests if a boolean column is not
false by just using the column name, pg_dump doesn't include parens
around the check constraint which causes a syntax error when reloading
the database.
Using the following to create a table:
create table test (col1 boolean
I have a fix for this in the patch queue and it will be applied in 24
hours. If you want to try it, it is at:
http://momjian.postgresql.org/cgi-bin/pgpatches
---
Bruno Wolff III wrote:
If you have a check
If you are referring to my patch, Bruce - that does not fix it. Mine
only addresses psql.
I don't think that pg_dump uses pg_get_constraintdef(). It's probably a
side effect of switching from using consrc to conbin.
Chris
Bruce Momjian wrote:
I have a fix for this in the patch queue and it
Christopher Kings-Lynne wrote:
If you are referring to my patch, Bruce - that does not fix it. Mine
only addresses psql.
I don't think that pg_dump uses pg_get_constraintdef(). It's probably a
side effect of switching from using consrc to conbin.
Oh, yea. If forgot the pretty printing
13 matches
Mail list logo
