RE: [CDBI] Using scalar functions with AbstractSearch

> I suppose it's my lack of experience with postgresql, but I find it a =

That's especially bizarre, and I'm fairly certainly it violates the SQL =
standard.  A scalar function or column function in ticks should always =
evaluate as a literal, not the function.

You're doing a comparison there though, what happens if you select NOW() =
and 'NOW()' as a result?

-Dylan

-----Original Message-----
From: Bill Moseley [mailto:moseley@xxxx.xxx]
Sent: Wednesday, February 01, 2006 9:23 PM
To: classdbi@xxxxx.xxxxxxxxxxxxxxxx.xxx
Subject: Re: [CDBI] Using scalar functions with AbstractSearch

On Thu, Feb 02, 2006 at 05:54:24AM +0100, Rhesa Rozendaal wrote:
> I suppose it's my lack of experience with postgresql, but I find it a =
bit=20
> unsettling that placeholder values would be executed instead of used =
as=20
> plain strings. I would not have expected

Does seem odd.

test=3D> select * from times where time < now();
 id | name  |          time         =20
----+-------+------------------------
  1 | hello | 2006-02-01 20:10:53-08
(1 row)

test=3D> select * from times where time < 'now()';
 id | name  |          time         =20
----+-------+------------------------
  1 | hello | 2006-02-01 20:10:53-08
(1 row)

--=20
Bill Moseley
moseley@xxxx.xxx

_______________________________________________
ClassDBI mailing list
ClassDBI@xxxxx.xxxxxxxxxxxxxxxx.xxx
http://lists.digitalcraftsmen.net/mailman/listinfo/classdbi

_______________________________________________
ClassDBI mailing list
ClassDBI@xxxxx.xxxxxxxxxxxxxxxx.xxx
http://lists.digitalcraftsmen.net/mailman/listinfo/classdbi