> > I am not absolutly happy with this because it looks like the
> > statement is not working correctly for 100%. It comes back with an
> > strange error message if the '%' sign is at the end of '40'!!..
> > select * from my_table where cast(my_int as text) like '40%';
> > ERROR: transformExpr: does not know how to transform node 103
> > Any ideas!..
> Thomas, I believe this is the problem with my processing a node twice.
> Do you have a fix for that, or should I make one?
tgl=> select * from t where cast(i as text) like '40%';
So, the patch for "function() BETWEEN" helps, but I'm still not sure it
is safe, since I don't know how these nodes might be handled deeper in
Also, one of my recent testing patches slightly breaks the type
conversion stuff so the numerology regression test fails on one of the
inserts and I haven't figured out which piece caused that. Nothing
should be affected in the CVS tree though.
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 1998-03-17 03:02:49|
|Subject: Re: [HACKERS] Unique index using hash?|
|Previous:||From: The Hermit Hacker||Date: 1998-03-17 02:47:57|
|Subject: Re: [HACKERS] Re: [PATCHES] patches for 6.2.1p6|