Hi All,
We've released version 1.0 of the Microsoft SQL Server 3rd Party Backend
for Django! We're excited to bring ongoing first class support to Django
users on SQL Server and Azure SQL DB.
@Will Vincent - we've reached out to your personal email in the hopes that
you can post about this rel
Hi All,
We've released version 1.0rc1 of the Microsoft SQL Server 3rd Party Backend
for Django, with support for Django 3.2 and JSONField.
We've re-added optional regex support so that the regex DLL file is
included in the pypi package as opposed to the source code. This follows
our organizat
Maybe wait with featuring till the licensing issues are cleared up.
https://github.com/microsoft/mssql-django/issues/15 does not leave a good
impression on a first glance.
On Friday, March 26, 2021 at 1:48:50 PM UTC+1 wi...@wsvincent.com wrote:
> Yes, what Adam said! We'll certainly feature the
Yes, what Adam said! We'll certainly feature the project next week in
Django News and would happily also include a blog post etc on the project :)
On Friday, March 26, 2021 at 7:56:11 AM UTC-4 Adam Johnson wrote:
> Great work Warren and co! I see you already have a number of stars on
> GitHub.
Great work Warren and co! I see you already have a number of stars on
GitHub.
A promotional blog post could help get the word out as well. If you do
write one, submit your blog's Django-specific feed to "Community blog
posts" on https://www.djangoproject.com/community/ and it will get picked
up by
Hi All,
We've released the preview version 1.0b1 of the Microsoft SQL Server 3rd
Party Backend for Django. This version supports Django 2.2, 3.0 and 3.1.
What's coming up next between now and GA release? We are re-adding optional
regex support, so that the regex DLL file is downloadable from a
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
wrote:
> > >
> > >
> > > Sean De La Torre wrote:
> > > > I've been maintaining/enhancing a ticket
> > > > (http://code.djangoproject.com/ticket/2358) contributed by another
> > > > django user that adds MSSQL support to django. In
;
> >
> > Sean De La Torre wrote:
> > > I've been maintaining/enhancing a ticket
> > > (http://code.djangoproject.com/ticket/2358) contributed by another
> > > django user that adds MSSQL support to django. In addition to what
> > > that user started, I&
maintaining/enhancing a ticket
> > (http://code.djangoproject.com/ticket/2358) contributed by another
> > django user that adds MSSQL support to django. In addition to what
> > that user started, I've added full introspection capabilities and
> > patched a few bugs tha
Sean De La Torre wrote:
> I've been maintaining/enhancing a ticket
> (http://code.djangoproject.com/ticket/2358) contributed by another
> django user that adds MSSQL support to django. In addition to what
> that user started, I've added full introspection capabilities an
I've been maintaining/enhancing a ticket
(http://code.djangoproject.com/ticket/2358) contributed by another
django user that adds MSSQL support to django. In addition to what
that user started, I've added full introspection capabilities and
patched a few bugs that I've found. I&
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
#x27;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, especially considering how fast
Django is evolving.
18 matches
Mail list logo
