Ah, that is very clear. My understanding was that LGPL code could be
used in a GPL project, but not necessarily vice-versa.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this
On 11/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Thanks. Any idea as to why adodb was used instead of native
> interaction?
>
By that, you mean FreeTDS via pymssql? It was GPL at the time, and
it's now LGPL. I think that's the only reason, though.
--~--~-~--~~-
Thanks. Any idea as to why adodb was used instead of native
interaction?
Sean De La Torre wrote:
> Take a look at this ticket http://code.djangoproject.com/ticket/2358
>
> It's based on adodb, and I believe it is fully functional except for
> paging support (hopefully coming soon).
>
> Sean
>
>
Take a look at this ticket http://code.djangoproject.com/ticket/2358
It's based on adodb, and I believe it is fully functional except for
paging support (hopefully coming soon).
Sean
On 11/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I am mostly new to Django, but have significant exp
I am mostly new to Django, but have significant experience working with
MSSQL in other languages. I noticed that there is support for MSSQL
(generating SQL only) through the adodb abstraction layer. I'm
guessing this was a compatibility patch to allow for the "TOP" vs
"LIMIT" syntax. Is that th
On 10/14/05, jws <[EMAIL PROTECTED]> wrote:
> I'd like to use Django for a project I am currently bidding on, but I
> need to know if MSSQL support will eventually be mainlined. I can
> tolerate some patchy-ness in the short term, but I don't want to
> maintain a parallel codebase for years, espec
Is anyone working on support for MS SQL Server? I've seen people
discuss it in the past, but have heard nothing specific regarding
'official' support. There's the following entry in the wiki, but
nothing more seems to be happening.
http://code.djangoproject.com/ticket/225
I'd like to use Django
