Re: [SQL] Usage of UUID with 8.3 (Windows)
Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> Figure out how to build ossp-uuid on Windows ... > > > > I think Windows has its own UUID generator, so the best bet would be to > > make that work. > > Only if it can be made to present the same SQL-level API as we have for > OSSP. Otherwise we'll be faced with boatloads of platform-dependent > client code ... Indeed. Linux, for example, also has "its own" UUID generator, but I intentionally used the OSSP library, because it is platform independent. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [SQL] PostgreSQL does not support updateable cursors
Premsun Choltanwanich wrote: > I found some information on internet about the PostgreSQL does not > support updateable cursors so I change my code to be read only cursors as > 'rsSystem.Open "SELECT * FROM v_memocatlist ORDER BY memocategory", > connSystem, adOpenForwardOnly, adLockReadOnly' then it work fine. However, > I need to use this query for make data ready to be updated on some record. > How can I fix this problem? 8.3 supports updatable cursors. Try that. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [SQL] Backward compatibility psql 8.1 to 8.2
Scott Marlowe wrote: > Does anyone who know about packaging know if this a limitation of the > packaging spec in rpm, or is there a relatively simple way to get an > rpm based machine to run >1 ver of pgsql at a time? The difference is merely that the packaging doesn't support that setup. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[SQL] comment on COLUMN, broken or misunderstanding?
I'm expecting COLUMN comments to work much like table comments, but I'm getting nothing back. Is this a reportable bug, or a misunderstanding? # comment on column sched.days is 'Bitmask 0=Sunday,7=Holiday, 8=School day, 9=Special'; COMMENT # \dd sched.days; Schema | Name | Object | Description +--++- (0 rows) # comment on table sched is 'Table comment'; COMMENT ez-sched=# \dd sched; Object descriptions Schema | Name | Object | Description +---++--- public | sched | table | Table comment (1 row) # select * from version(); PostgreSQL 8.2.6 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.2.1 (SUSE Linux) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [SQL] comment on COLUMN, broken or misunderstanding?
Bryce Nesbitt <[EMAIL PROTECTED]> writes: > I'm expecting COLUMN comments to work much like table comments, but I'm > getting nothing back. Is this a reportable bug, or a misunderstanding? > # comment on column sched.days is 'Bitmask 0=Sunday,7=Holiday, 8=School > day, 9=Special'; > COMMENT > # \dd sched.days; > Schema | Name | Object | Description > +--++- > (0 rows) Try "\d+ sched". I don't think \dd considers columns at all --- what that command would be looking for is comments on table days in schema sched. regards, tom lane ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [SQL] comment on COLUMN, broken or misunderstanding?
2008/2/18, Bryce Nesbitt <[EMAIL PROTECTED]>: > I'm expecting COLUMN comments to work much like table comments, but I'm > getting nothing back. Is this a reportable bug, or a misunderstanding? Try \d+ sched Markus ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [SQL] comment on COLUMN, broken or misunderstanding?
Bryce Nesbitt написа: I'm expecting COLUMN comments to work much like table comments, but I'm getting nothing back. Is this a reportable bug, or a misunderstanding? [...] Misunderstanding I would say - "\dd" is for objects and they are: '"Object" covers aggregates, functions, operators, types, relations (tables, views, indexes, sequences, large objects), rules, and triggers.' (http://www.postgresql.org/docs/8.2/static/app-psql.html, look for "\dd"). You could see the comment for the column with "\d+ table_name". -- Milen A. Radev ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [SQL] comment on COLUMN, broken or misunderstanding?
On Sun, Feb 17, 2008 at 06:18:26PM -0800, Bryce Nesbitt wrote: > I'm expecting COLUMN comments to work much like table comments, but I'm > getting nothing back. Is this a reportable bug, or a misunderstanding? > > # comment on column sched.days is 'Bitmask 0=Sunday,7=Holiday, 8=School > day, 9=Special'; > COMMENT > # \dd sched.days; > Schema | Name | Object | Description > +--++- > (0 rows) You're using the wrong psql command. Try "\d+ sched". -- Michael Fuhr ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
