On Wed, Aug 25, 2004 at 12:10:39AM -0400, Matt Wilson wrote: > 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?
Not complaining, pysqlite is very conformant AFAICT. > > * 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). Yeah, it's read-only, though, (no __setitem__), you have to "cast" to a dict if you want to use the rows in your app. > > * I'd like to have more transparent handling of bools. > > Example? Currently you have to use the "--types" hack if you use a BOOL column type (which I only use as a way to communicate to my app how the data should be displayed.) I avoid the --types hack by converting the value to an int after retrieval and before setting it back, but I'd rather not have to worry about it. > > * 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...) Works great currently. I have a need for an interval type, although previously I've just used strings and converted them only when I need to add them up. Dave Cook
