[SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Tomas Doran
I'm not sure if this is a bug, or not - but it looks like one to me. if you say: CREATE TABLE testtable ( col1 char(1), data text ); INSERT INTO testtable (col1, data) VALUES ('1', 'foobar'); INSERT INTO testtable (col1, data) VALUES ('2', 'foobarbaz'); The following queries all

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Peter Eisentraut
Am Donnerstag, 24. Mai 2007 13:20 schrieb Tomas Doran: CREATE TABLE testtable (      col1   char(1),     data   text ); The following queries all work: INSERT INTO testtable (col1, data) VALUES (3::int, 'foobarbazquux'); SELECT * FROM testtable WHERE col1 = 3::int; SELECT * FROM testtable

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Tomas Doran
On 24 May 2007, at 12:34, Marcin Stępnicki wrote: Dnia Thu, 24 May 2007 12:20:54 +0100, Tomas Doran napisał(a): CREATE TABLE testtable ( col1 char(1), data text ); INSERT INTO testtable (col1, data) VALUES ('1', 'foobar'); INSERT INTO testtable (col1, data) VALUES ('2',

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Richard Huxton
Tomas Doran wrote: On 24 May 2007, at 12:34, Marcin Stępnicki wrote: I'm not sure if I understand you correctly, but it seems that you are comparing apples to oranges here (integer and character values). Yep, totally - it's not nice, but we need to do it at $ork for hysterical raisins..

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Marcin Stępnicki
Dnia Thu, 24 May 2007 12:54:48 +0100, Tomas Doran napisał(a): If I can do something to make it work in the postgres backend, then that'd be acceptable, and I'm investigating that.. From what I know it's impossible without touching the source. This is, at the very least, is a glaring

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Tomas Doran
On 24 May 2007, at 13:19, Richard Huxton wrote: Tomas Doran wrote: On 24 May 2007, at 12:34, Marcin Stępnicki wrote: I'm not sure if I understand you correctly, but it seems that you are comparing apples to oranges here (integer and character values). Yep, totally - it's not nice, but we

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Tom Lane
Tomas Doran [EMAIL PROTECTED] writes: The tightening in general is biting me, but if the answer was 'it was deliberate tightening', and the behavior was consistent, then we'd have just dealt with it - it's the in-consistent behavior that makes me think this is a bug (or at least a

Re: [SQL] Potential bug in postgres 8.2.4

2007-05-24 Thread Tomas Doran
On 24 May 2007, at 15:51, Tom Lane wrote: Tomas Doran [EMAIL PROTECTED] writes: The tightening in general is biting me, but if the answer was 'it was deliberate tightening', and the behavior was consistent, then we'd have just dealt with it - it's the in-consistent behavior that makes me