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:
&
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
--~--~-~--~~~--
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.)
&
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
th
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 iterator(s
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)
DATA_TYPES
