From: | Per Rønne <per(at)idp(dot)dk> |
---|---|
To: | Per Rønne <per(at)idp(dot)dk>, "'pgsql-interfaces(at)postgresql(dot)org'" <pgsql-interfaces(at)postgreSQL(dot)org> |
Subject: | RE: [INTERFACES] Possible error in libpg++ interface, date[time] fields. |
Date: | 1999-04-22 13:53:16 |
Message-ID: | B15FE41977A9D21195F00000836A4275119CCB@mars.idp.dk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
My investigations show me that if null fields are present, nothing is
returned. Thus fields "right" of a null field will be moved left one field.
I think the same mighthappen if you use varchar strings instead of
fixed-length strings. If a string s is declared as char(n), and the actual
size of s is 2 and n >= 2, the next field will be moved n - 2 chars to the
left in the string that contains the result of the query.
--
Per Erik Rønne
E-mail per(at)idp(dot)dk (office)
Telephone +45 32 83 63 17 (office), +45 26 16 48 10 (mobile)
-----Original Message-----
From: Per Rønne [mailto:per(at)idp(dot)dk]
Sent: 22. april 1999 11:35
To: Per Rønne; 'pgsql-interfaces(at)postgresql(dot)org'
Subject: RE: [INTERFACES] Possible error in libpg++ interface, date[time]
fields.
Further experiments show that the row marks mentioned - NULL values in the
row, at least NULL values in fields _before_ the field in question.
[SNIP the original message - article otherwise too long]
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1999-04-22 15:50:17 | Re: [INTERFACES] ecpg cursors and scope |
Previous Message | José Soares | 1999-04-22 12:02:09 | Re: [INTERFACES] Detecting existance of table |