not to add fuel to the debate, but ...
theres already ##sys#null-pointer defined (as a procedure that returns a null
pointer).. a) its already defined, b) it has the same semantics as a NULL,
c) it should be equivalent in the sense of eq? , i think...
(define sql-null (##sys#null-pointer))
would ensure that theyre equivalent in every sense of the term, one would think.
-elf
On Sun, 2 Mar 2008, Graham Fawcett wrote:
On Sun, Mar 2, 2008 at 9:56 PM, Elf <[EMAIL PROTECTED]> wrote:
out of curiousity, how can sql be returning symbols, ever? enums are integers,
yes?
Hi Elf,
My reasoning was that I don't want to needlessly restrict what a
database driver returns. In Postgresql's case, for example, the
database can define custom datatypes. It may be possible that a custom
type is best represented by a symbol. When your db has builtin
datatypes for arrays, circles, polygons and MAC addresses, and has an
open system for defining anything else, it broadens one's horizons
somewhat. :-)
In Postgres, Enums are string values in a restricted set. (I gave that
as a *possible* case where symbols might make sense, since they are
interned strings.)
Best,
Graham
_______________________________________________
Chicken-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/chicken-users
