Ozzi Lee scripsit: > Let me know what you think. If someone's already got something going I'd > like to pitch in as well.
I suggest that a row be an a-list, and that null columns be represented by being non-existent in the a-list. If you end up preferring a plain list or a vector, then use (void) instead -- I am trying to get this standardized as the Chicken representation of SQL's NULL. In reality, though, I think portability between databases is more hypothetical than real. Projects typically start with one database and stick to it, for moving between databases *even if a portability layer is in use* turns out to be hard -- all sorts of stuff outside the main code base ends up changing (path names, load scripts, whatever). -- You let them out again, Old Man Willow! John Cowan What you be a-thinking of? You should not be waking! [EMAIL PROTECTED] Eat earth! Dig deep! Drink water! Go to sleep! Bombadil is talking. http://ccil.org/~cowan _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
