[SQLObject] Re: Design questions

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

I copied this to the list because this exactly the sort of discussion 
the list is for...

On Tuesday, October 28, 2003, at 10:25 PM, James Ralston wrote:
> Ian,
>
> I've just been tasked with the unpleasant job of writing a web based 
> application using MSSQL as the backend database.  To add insult to 
> injury, it has to run on Solaris.  The server will probably have an 
> ODBC driver installed to make the leap.  Long story short: if I am 
> able to do the app in python, I would not be able to use SQLObject in 
> it's current form.
>
> My questions:
> 1) What do you think of (me) making some changes to DBConnection to 
> support an ODBCConnection (with minor alterations to all of the 
> connection classes to allow use/wrapping as a "dialect" )?

What kind of flexibility are you looking for?  Someone else using ODBC 
(Magnus Lycka?) wanted to keep parameters separate so that the database 
driver could handle the quoting.  Maybe the same issue as you are 
having.

Another option would be to use the database name to greater effect.

> 2) I know you prefer OSS db's (as do I), but do you mind the addition 
> of an MSSQLConnection (really it would be more like "a completion" of 
> the Sybase stuff currently branched in cvs)?

Yeah, that's fine.  I just can't support non-OSS databases.

The stuff doesn't really have to be a branch, I don't think, though 
maybe it touches things more than I'm expecting.

> BTW, I found a semi-solution to the kinterbasdb iterator issue, but it 
> only added to the firebird autocommit "hack."  The solution involves 
> setting retaining=1 to the conn.commit call (or adding an even more 
> hackish shouldRetain attribute to the _iterSelect call in the DBAPI 
> class).  I played with it on my machine, but I am reluctant to let 
> this code be seen in public :-)

What is retain supposed to mean?

--
Ian Bicking | ia...@co... | http://blog.ianbicking.org