From: Bud P. B. <bu...@si...> - 2003-04-30 19:21:31
|
On 30 Apr 2003 12:29:01 -0500 Nick <ni...@dd...> wrote: > I'll buy that... that's also what psycopg returns. So, should the > naming be in accordance with Python types or with SQL types? I think with SQL types. After all, the decisions about the best physical representation of python types cannot be made automatically (there are many options...). So there seems no way of avoiding to deal with SQL. [Is this true? I adapted this conviction from lower-level languages that require more decisions on physical representation than Python] There is some friction with this approach tough: * expressing decisions in SQL terminology is not natural for non-SQL backends * sticking to standard SQL terminology is not natural with non-standard SQL dbms... --b |