r support for setting up my django project with MS SQL server.
>
> As there is no proper tutorial how to setup with MS SQL server. I tried it
> many times but failed with same errors. Please help me to progress.
>
> Tried below :
> 'ods_database': {
> 'ENGINE': 'sql_server.py
try this
https://django-mssql.readthedocs.io/en/latest/quickstart.html#dependencies
OR
https://stackoverflow.com/questions/43430091/connecting-django-with-mssql-server
On Wed, 7 Oct 2020 at 20:36, arun sahu wrote:
> Hi Geeks,
>
> I need your support for setting up my django project wi
Hi Geeks,
I need your support for setting up my django project with MS SQL server.
As there is no proper tutorial how to setup with MS SQL server. I tried it
many times but failed with same errors. Please help me to progress.
Tried below :
'ods_database': {
'ENGINE
I use it for several applicartions. Not sure that there is any difference
with the various versions of sql server, except for minor syntax issues.
What did you want to know?
The performance is very good.
I have one application in which I use the admin interface which uses the
ORM and I have
Hi all,
Can anyone share his experience about developing application with django
that uses Microsoft SQL server 2005 or later ?
And how is it in production environment.
Thanks
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this
Good morning all,
Can someone share with me its experience with Django application running on
MS SQL DB? I have a heavy application that i want to migrate to django.
Please can you share your experience with me in term of stability and
feasibility? How does django teamup with MS SQL.
Regards
Cheng Zhang wrote:
Hi Cheng,
> Actually my previous statement isn't correct, I just realized that
> pymssql also claimed to work on Windows, except it will use M$'s
> native libraries instead of FreeTDS.
You worked this out quicker than I ever could have. Thanks.
Ok, the patch is away [http://code.djangoproject.com/ticket/1258]. :-)
- Cheng Zhang
On 1/20/06, Cheng Zhang <[EMAIL PROTECTED]> wrote:
> > Adapter class over adodbapi where supported, falling back to pymssql?
>
> I think they (ado_mssql and pymssql) are meant for different OS
> platforms, in that ado_mssql is for Django running on Windows to
> connect to SQL Server since it only
On Jan 13, 2006, at 12:40 AM, Jeremy Dunck wrote:
On 1/12/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
The pymssql driver only supports DB-LIB, which is way outdated and
you
wont have access to functionality added to MSSQL after version 6.5.
This is not the best option IMHO.
Adapter class
Actually that's incorrect. Pymssql is only a thin wrapper around
FreeTDS library (http://www.freetds.org/).
AFAIK, FreeTDS works with SQL-Server 2000 pretty well.
- Cheng
On Jan 13, 2006, at 12:15 AM, Rich Bakos wrote:
Jeroen Ruigrok van der Werven wrote:
Hi Jeroen,
Can a bunch of us
Jeremy Dunck wrote:
> On 1/11/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > think adodbapi DOES use parameterization. It's just slightly
> > non-standard. (thus, the %s -> ? stuff above)
>
> I was surprised by this, by the Python DB API allows for parameters in
> the string supplied to the
On 1/12/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>
> On 1/12/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
> > The pymssql driver only supports DB-LIB, which is way outdated and you
> > wont have access to functionality added to MSSQL after version 6.5.
> > This is not the best option IMHO.
>
>
On 1/12/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
> The pymssql driver only supports DB-LIB, which is way outdated and you
> wont have access to functionality added to MSSQL after version 6.5.
> This is not the best option IMHO.
Adapter class over adodbapi where supported, falling back to
On 1/10/06, Cheng Zhang <[EMAIL PROTECTED]> wrote:
> As matter of fact, I am trying to make pymssql backend for Django
> work since in my current project we have to inherit a MS-SQL
> database. Changing the database is definitely not an option. If
> Django can be used with MS-SQL, then I can
Actually...SQL Server would cache the execution plan anyway. It's
gotten smart enough to do that now. (When parsing the statement, it
recognizes the "style", and caches the plan like it would for a
parameterized query. They call it auto-parameterization, IIRC.).
Parameters improve the db engine's
On Tue, 10 Jan 2006 14:33:18 -0600 Adrian Holovaty wrote:
> The problem is that the SQL Server database backend (the "adodbapi"
> library) assumes placeholders use "?" for placeholders. So the Django
> layer needs to convert all "%s" placeholders in the query to "?".
>
> It looks like the
Jeremy Dunck wrote:
Hi Jeremy,
> Yeah, adodbapi was doing something weird with the executeHelper, so we did
> this:
Yeah I worked that out but haven't gotten too far. I had to make a
modification to function_get_sql_clause to support the MS TOP keyword.
Also had to modify method_save to
On 1/10/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 1/10/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
> > Here is the exact SQL that is passed to MS SQL:
> >
> > SELECT
> > [core_sessions].[session_key],[core_sessions].[session_data],[core_sessions].[expire_date]
> > FROM [core_sessions]
On 1/10/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
> Here is the exact SQL that is passed to MS SQL:
>
> SELECT
> [core_sessions].[session_key],[core_sessions].[session_data],[core_sessions].[expire_date]
> FROM [core_sessions] WHERE [core_sessions].[session_key] = %s
>
> As you can see, it has
On Jan 10, 2006, at 10:21 PM, Adrian Holovaty wrote:
On 1/9/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
I am experimenting with Django and MS SQL and it appears that
Django is
passing parameters to MS SQL in an incorrect format.
The params are being passed in as a format string sty
Jeremy Dunck wrote:
Hi Jeremy,
> > The syntax that MS SQL expects:
> > select foo from bar where foo = @fooName
>
> Are we talking about literals or parameters?
I'm talking about parameters.
> That is, are you expecting:
>
> select colname from tablename where colname = 'somevalue'
> or
>
Adrian Holovaty wrote:
Hi Adrian,
> Could you paste the entire traceback you get? Also, would any other MS
> SQL users in the audience be able to help?
Here is an entire traceback I get when attempting to access the /admin
site:
Traceback (most recent call last):
File
>total waste of time - foss rulz - let them come to us
There are people having a real job and those might stumble over mssql
servers (I know for sure that I will from time to time) and they might
find it comforting to know that they can continue to use their
framework of choice. And no, they
Wilson wrote:
Django supporting MSSQL strikes me a bit like iTunes running on
Windows. As in it's a great thing for the platform. If somebody locked
in to a MSSQL environment has the chance to try a real project with
Django and be exposed to great, useful open-source software that
doesn't turn
Django supporting MSSQL strikes me a bit like iTunes running on
Windows. As in it's a great thing for the platform. If somebody locked
in to a MSSQL environment has the chance to try a real project with
Django and be exposed to great, useful open-source software that
doesn't turn its nose up at
On Tuesday 10 Jan 2006 9:46 pm, Jeremy Dunck wrote:
> I'm philosophically in line with much of the Free philosophy, but
> FSF didn't decide not to run on Unix while developing the tools
> to replace it; some compromises are necessary. There exists a
> huge install base locked
s a huge install base
locked into MS SQL; denying django to those folks won't help them get
away from the platform you so despise.
Nonviolence is the way. ;-)
On Tuesday 10 Jan 2006 9:24 pm, Adrian Holovaty wrote:
> On 1/10/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> > > The majority of users are on SQL Server 2000. A significant
> > > minority are on 7. A tiny minority still use 6.5. And in a
> > > year, a significant minority will be using
On 1/10/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> > The majority of users are on SQL Server 2000. A significant
> > minority are on 7. A tiny minority still use 6.5. And in a
> > year, a significant minority will be using 2005.
>
> and which is opensource? and if it is not, why waste our
On Tuesday 10 Jan 2006 9:06 pm, Jeremy Dunck wrote:
> On 1/10/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> > and which is opensource? and if it is not, why waste our time?
>
> If you're going to take that position, I think you mean Free.
>
> But we're not wasting your time, we're wasting
On 1/10/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> and which is opensource? and if it is not, why waste our time?
>
If you're going to take that position, I think you mean Free.
But we're not wasting your time, we're wasting ours. Feel free to
ignore the discussion.
On Tuesday 10 Jan 2006 8:39 pm, Jeremy Dunck wrote:
> > best to target the latest open source version
>
> I assume you're being ironic there.
>
> The majority of users are on SQL Server 2000. A significant
> minority are on 7. A tiny minority still use 6.5. And in a
> year, a significant
On 1/10/06, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
>
> On Tuesday 10 Jan 2006 8:20 pm, Jeroen Ruigrok van der Werven wrote:
> > Which version of MS SQL do you initially want to target Adrian?
>
> best to target the latest open source version
I assume you're being ironic there.
The
On 1/10/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
> The syntax that MS SQL expects:
> select foo from bar where foo = @fooName
Are we talking about literals or parameters?
That is, are you expecting:
select colname from tablename where colname = 'somevalue'
or
select colname from tablename
On Tuesday 10 Jan 2006 8:20 pm, Jeroen Ruigrok van der Werven wrote:
> Which version of MS SQL do you initially want to target Adrian?
best to target the latest open source version
--
regards
kg
http://www.livejournal.com/users/lawgon
tally ho! http://avsap.org.in
ಇಂಡ್ಲಿನಕ್ಸ வாழ்க!
On 1/10/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> Which version of MS SQL do you initially want to target Adrian? I can
> probably get some basic testing done here to clear the majority of the
> issues.
Thanks for the offer! Knowing next to nothing about MS SQL, I don't
have
On 1/10/06, Rich Bakos <[EMAIL PROTECTED]> wrote:
> The params are being passed in as a format string style (%s), which MS
> SQL chokes on.
Can you clarify exactly what you mean here? What SQL are you getting,
and what are you expecting (or what would work)?
If you feel like having a poke
I am experimenting with Django and MS SQL and it appears that Django is
passing parameters to MS SQL in an incorrect format.
The params are being passed in as a format string style (%s), which MS
SQL chokes on.
Is anyone here using MS SQL that might be able to shed some light on
this problem
39 matches
Mail list logo
