On Tue, Aug 24, 2004 at 08:43:47PM -0700, David M. Cook wrote: > > * DBAPI compliance is important to me. sqlite is only one of the DBs I'd > like to support in my apps.
Do you know what's currently lacking in conformance? > * I use pyformat pretty heavily. I like being able to use dictionaries as a > data format, and pyformat makes this really easy. But it would probably not > be too hard to create a wrapper for this (there's already a cookbook > recipe for this.) Right. Writing a wrapper wouldn't be too hard. But I would like to encourage the use of standard format SQL and keep the binding as light-weight as possible. I don't see a problem implementing this at a higher level as a wrapper. > * A dictionary-like row object would be nice (pyPgSQL has this). Currently > pysqlite has read-only row objects. But his is not that important as it > is easy to convert tuples to dicts. pysqlite already had that, as does pysqlite3 (see the Row class). > * I'd like to have more transparent handling of bools. Example? > * I do like the current pysqlite's transparent handling of date/time types. How could it be better? (of course, pysqlite3's handling is non existent...) > * Not having having the "--types" hack is not a loss IMO, as I find it > rather awkward. You have to build a string of types for each possible > query you might do, and it's very specific to pysqlite. Yes, definitely. I haven't needed user-defined types in any code I've written. Some method to allow user-defined types to be registered would be nice, but it's going to be an pysqlite-specific extension, which would be good to avoid...
