[SQLObject] Big API changes are coming
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Oleg B. <ph...@ph...> - 2006-10-23 13:23:12
|
Hello! I am going to start working on a number of rather large issues, and few of them are really big changes. I will describe them in greater details below, but now I want to ask a question: how should I handle the changes? I can release SQLObject 0.8 from the trunk and start to work on these large issues; then they will be in the SQLObject 0.9. Or I can continue to work in the trunk now, so the changes will be in SQLObject 0.8, but the release will be much later. What is better for the SQLObject users? The biggest issue I am going to work on is Unicode support. It is now clear that my original decision to allow an every UnicodeCol to has its own dbEncoding was a mistake. I would like to repair it. I am going to remove dbEncoding from UnicodeColumns and move it to DBConnection. Every connection could have dbEncoding; the encoding will be used to convert: -- strings queries to unicode and unicode results to strings for those DB API drivers that accept and return unicode: latest MySQLdb and PySQLite; -- unicode queries to string and string results to unicode columns for those DB API drivers that don't work with unicode. The second big issue is %-encoded DB URIs. I'd like to change the URI encoding to be a proper %-encoding. This allow users to use standard tools (urllib) to generate queries that contain special characters, and allows the developers to use the same standard libraries to parse the encoded URIs. But is a big change as it requires everyone to reencode their DB URIs. I am going to start obsoleting support for Python 2.2. The first step will be to issue a warning. I am not sure if SQLObject 0.8 should issues the warning, or should I wait for SQLObject 0.9? There is also a few lesser issues, not as world shuttering. I am going to work on sqlbuilder.Select() to synchronize its features with SQLObject.select(). Even lesser is to implement fromDatabase for SQLite - the last database that lacks the feature. Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |