Re: [HACKERS] Weird constraint output

2003-08-29 Thread Christopher Kings-Lynne
Obviously psql uses either use pg_constraint.consrc or pg_get_expr(conbin, conrelid) which both will give this lot of parentheses, so it's not a bug, but a feature For easier reengineering, I invented several pg_get_xxx functions with a pretty-print option, which omits this messy parentheses,

Re: [HACKERS] Weird constraint output

2003-08-29 Thread Andreas Pflug
Christopher Kings-Lynne wrote: I have changed psql to use pg_get_viewdef(oid, true). I agree with Tom for not using it in dumps just yet though. While there still might be a pg_dump option to do this. Is there a function for getting nice constraint defs? Of course there is, use

[HACKERS] Weird constraint output

2003-08-28 Thread Jeroen Ruigrok/asmodai
[Please hold me on the to:/cc: list since I am not subscribed] After talking this over with some of the great guys on IRC it was suggested I ask here. I am currently working on a document about how to convert from MySQL to PostgreSQL (Sybase, Oracle, DB2, MS SQL Server are also going to be

Re: [HACKERS] Weird constraint output

2003-08-28 Thread Andreas Pflug
Jeroen Ruigrok/asmodai wrote: Check constraints: bugs_severity_cstr ((bug_severity = 'blocker'::character varying) OR (bug_severity = 'critical'::character varying) OR (bug_severity = 'major'::character varying)) If you have even more choices there (as Bugzilla does) you even get: CONSTRAINT