Re: MS SQL pyodbc backend update to trunk

2008-07-18 Thread vcc
Fixed, thanks. - Original Message - From: "bob84123" <[EMAIL PROTECTED]> To: "Django developers" <django-developers@googlegroups.com> Sent: Wednesday, July 16, 2008 7:51 AM Subject: Re: MS SQL pyodbc backend update to trunk Thanks for that. Tur

Re: MS SQL pyodbc backend update to trunk

2008-07-17 Thread bob84123
Hi all. Sorry about the noise before regarding DateField/TimeField.. it wasn't an issue specific to this backend. It's actually a django problem - details and fix at http://code.djangoproject.com/ticket/7801 Thanks. On Jul 16, 9:51 am, bob84123 <[EMAIL PROTECTED]> wrote: > Thanks for that.  

Re: MS SQL pyodbc backend update to trunk

2008-07-15 Thread bob84123
Thanks for that. Turned out the problem I was having was to do with slicing queries where no order_by was explicitly specified. I've uploaded a slightly modified patch to the same place. On Jul 15, 6:19 pm, "Ramiro Morales" <[EMAIL PROTECTED]> wrote: > On Tue, Jul 15, 2008 at 12:53 AM,

Re: MS SQL pyodbc backend update to trunk

2008-07-15 Thread Ramiro Morales
On Tue, Jul 15, 2008 at 12:53 AM, bob84123 <[EMAIL PROTECTED]> wrote: > > Yes I am. > See patch attached to issue #2 I just opened: http://code.google.com/p/django-pyodbc/issues/detail?id=2 Regards, -- Ramiro Morales --~--~-~--~~~---~--~~ You received this

Re: MS SQL pyodbc backend update to trunk

2008-07-14 Thread bob84123
Yes I am. On Jul 15, 11:51 am, "Ramiro Morales" <[EMAIL PROTECTED]> wrote: > On Mon, Jul 14, 2008 at 10:09 PM, bob84123 <[EMAIL PROTECTED]> wrote: > > > (It also seems order_by is recently broken, I'm going to have a look > > into that now.) > > Are you using SQL server 2000? > > Regards, > > --

Re: MS SQL pyodbc backend update to trunk

2008-07-14 Thread Ramiro Morales
On Mon, Jul 14, 2008 at 10:09 PM, bob84123 <[EMAIL PROTECTED]> wrote: > > (It also seems order_by is recently broken, I'm going to have a look > into that now.) Are you using SQL server 2000? Regards, -- Ramiro Morales --~--~-~--~~~---~--~~ You received this

Re: MS SQL pyodbc backend update to trunk

2008-07-14 Thread bob84123
I've fixed a couple of little issues in the backend: - Settings.DATABASE_ODBC_DRIVER never got included in the connection string so I put it in at the start; - I changed the way parameters with default values are checked from "if not settings.PARAM" to "if 'PARAM' not in dir(settings)", because

Re: MS SQL pyodbc backend update to trunk

2008-07-14 Thread Leo Soto M.
On Thu, Jul 10, 2008 at 5:25 AM, vcc <[EMAIL PROTECTED]> wrote: > > Thanks Malcolm tredinick, your greate Queryset-refactor work make > write a backend very clear, thanks again! > Yes, make a external database backend is better now, I clean the code > and get it done! I just upload source code to

Re: MS SQL pyodbc backend update to trunk

2008-07-10 Thread vcc
Thanks Malcolm tredinick, your greate Queryset-refactor work make write a backend very clear, thanks again! Yes, make a external database backend is better now, I clean the code and get it done! I just upload source code to django-pyodbc code.google project, and I join this project to continue

Re: MS SQL pyodbc backend update to trunk

2008-07-08 Thread bob84123
Looks like this backend is going quite well. For what it's worth, I solved the other end of the datetime/date/time problem by patching django.db.models.query.QuerySet.iterator. I expect there's a better solution than this but I thought I'd post this because it at least works. def

Re: MS SQL pyodbc backend update to trunk

2008-07-08 Thread Malcolm Tredinnick
On Tue, 2008-07-08 at 21:26 +0800, vcc wrote: > Thanks for Russ Magee, I see. > > I just updated this backend, it's look like everything work fine for me. I > have some projects working with this backend, I'll keep improve it. Please > check the patch in the attachments. So the best thing to

Re: MS SQL pyodbc backend update to trunk

2008-07-08 Thread James Bennett
On Tue, Jul 8, 2008 at 8:26 AM, vcc <[EMAIL PROTECTED]> wrote: > I just updated this backend, it's look like everything work fine for me. I > have some projects working with this backend, I'll keep improve it. Please > check the patch in the attachments. As Russ, and the many previous threads

Re: MS SQL pyodbc backend update to trunk

2008-07-07 Thread bob84123
I'd like to thank you for this work. I tried it and it *mostly* works on my Windows Server 2003 machine with MS SQL Server 2000, with a few hacks: - Changed the last line in creation.py to (this was just to make it work in SQL 2000 *for me*, clearly it shouldn't stay like this)

Re: MS SQL pyodbc backend update to trunk

2008-07-02 Thread Russell Keith-Magee
On Wed, Jul 2, 2008 at 9:48 PM, vcc <[EMAIL PROTECTED]> wrote: > I port MS SQL pyodbc backend (django-pyodbc) to newforms-admin r7671, tested > on ubuntu 8.04 and with SQL Server 2005. > I found sql server need convert boolean value to integer (BooleanField), so > need add a new feature like

MS SQL pyodbc backend update to trunk

2008-07-02 Thread vcc
I port MS SQL pyodbc backend (django-pyodbc) to newforms-admin r7671, tested on ubuntu 8.04 and with SQL Server 2005. I found sql server need convert boolean value to integer (BooleanField), so need add a new feature like 'needs_bool_to_integer' to DatabaseFeatures, deafult to False. Since