Re: [SQLObject] naming conventions

[Ian B. <ia...@co...>]

On Wed, 2003-04-30 at 15:49, Ian Bicking wrote:
> I'm not sold on using Python types, though I suspect there will be more
> confusion if I use SQL types (like DateTimeCol in MySQL, vs.
> TimestampCol in Postgres).  We can all agree on the Python types,
> because there's only one Python, but there's many databases, not all of
> which adhere to the SQL standard (DBMConnection obviously does not, for
> instance, nor would MetaKit).

I'm now feeling more convinced that I should stick to using Python type
names, not SQL names.  In particular, I've been working on this form
stuff, and handling situations where I'm translating from HTTP variables
(i.e., strings) to Python types.  A lot of the same concepts apply to
getting data from SQL, or XMLRPC -- so I'd like for their to be one way
of specifying the type/constraint information.  Python is the only
option, since it's the one thing all the data sources have in common --
the Python destination.

  Ian