On Tue, 2008-04-01 at 10:10 -0700, Adam V. wrote:
> In DateTimeField.get_db_prep_save there is a hard-coded check for the
> mysql backend, which drops the microseconds from the value.
>
> I'm working on an external MS SQL backend (django-mssql) and I'm
> running into a different problem here.
>
> I have a patch in my backend already, to enable regex searches in MS
> SQL. I think this is reasonable, as you have to install either a COM
> or CLR extended stored procedure in your database to get this
> functionality. Inserting values in a DateTimeField is perhaps a bit
> more basic a functio
> I think that it's perfectly OK to distribute a patch to change the
> hardcoded functionality -- it's far better than trying to monkey-patch
> the code under active development.
I have a patch in my backend already, to enable regex searches in MS
SQL. I think this is reasonable, as you have to i
On Apr 1, 9:10 pm, "Adam V." <[EMAIL PROTECTED]> wrote:
> In DateTimeField.get_db_prep_save there is a hard-coded check for the
> mysql backend, which drops the microseconds from the value.
>
> I'm working on an external MS SQL backend (django-mssql) and I'm
> running into a different problem here
In DateTimeField.get_db_prep_save there is a hard-coded check for the
mysql backend, which drops the microseconds from the value.
I'm working on an external MS SQL backend (django-mssql) and I'm
running into a different problem here.
DateTimeFields are sent to queries as unicode which looks like
