Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-27 Thread Leo Soto M.
On 12 jun, 21:37, "Leo Soto M." <[EMAIL PROTECTED]> wrote: > On Thu, Jun 12, 2008 at 8:35 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote: > [...] > > > Since then I've opened ticket [2]#7420 with a patch > > I see that part of the patch deals with the fact that the underlying > adapter prefer to rec

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-18 Thread mamcx
Excellent. This could be added to google code? Is more easy run on trunk thta doing the patching dance... I test this shortly. I hope we could do this and prove that is doable to all the *nix db guys ;) --~--~-~--~~~---~--~~ You received this message because you

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-16 Thread Ian Kelly
On Mon, Jun 16, 2008 at 5:10 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote: > /me greps over the cx_Oracle 4.3.3 and 4.4 source trees. > > It's me or cx_Oracle doesn't have an autocommit symbol at all?. In > fact, it hasn't > a set_isolation_level one either. It does as of version 4.3.2. I know t

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-16 Thread Ivan Illarionov
> To solve it I proposed[1] another strategy: delegate type conversion > to the backend. Otherwise, I think we will end with too many backend > flags. +1 I maintain the external Firebird backend and I would also prefer this solution. Ivan Illarionov --~--~-~--~~~---~

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-16 Thread Ramiro Morales
Ian, On Thu, Jun 12, 2008 at 10:49 PM, Ian Kelly <[EMAIL PROTECTED]> wrote: >> connection.autocommit is an attribute and not a method (didn't find a way to >> cleanly monkeypatch this). > > It's also an attribute in cx_Oracle. I'll have to take a look at it > some time and figure out why it's no

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-13 Thread Adam V.
> To solve it I proposed[1] another strategy: delegate type conversion to the > backend. +1 I maintain the external django-mssql backend, and I would HUGELY prefer to get "real Python types" instead of to-string types for things like dates/times/decimal/etc. (Converting everything to strings "f

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-12 Thread Ian Kelly
On Thu, Jun 12, 2008 at 6:35 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote: > Since then I've opened ticket [2]#7420 with a patch that would reduce the list > of things needed to patch in Django to just *one item: Taking in account the > fact that in pyodbc seems to be the only DB-API2 adapter wher

Re: MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-12 Thread Leo Soto M.
On Thu, Jun 12, 2008 at 8:35 PM, Ramiro Morales <[EMAIL PROTECTED]> wrote: > > Jack Moffitt, mamcx (and everyone interested), > > I've been working in my free time for the last few days on updating the > pyodbc-based MS SQL Server backend so it a) can be an external Django > backend and b) to post

MS SQL backend as a proper external backend (was: RFC: Django 1.0 roadmap and timeline)

2008-06-12 Thread Ramiro Morales
Jack Moffitt, mamcx (and everyone interested), I've been working in my free time for the last few days on updating the pyodbc-based MS SQL Server backend so it a) can be an external Django backend and b) to post qs-rf merge. First I tried to participate by testing django-pyodbc and opening a [1]