validation aware models? or check constraints?

hi all, a while back(http://groups.google.com/group/django-developers/ browse_thread/thread/fef854223b97e49c/c0e0ccce78369f05? lnk=gst&q=validation+aware+models&rnum=4#c0e0ccce78369f05) there was a discussion about adding a way to perform validation before saving an object. As far as I see we co

validation aware models? or check constraints?

hi all, a while back(http://groups.google.com/group/django-developers/ browse_thread/thread/fef854223b97e49c/c0e0ccce78369f05? lnk=gst&q=validation+aware+models&rnum=4#c0e0ccce78369f05) there was a discussion about adding a way to perform validation before saving an object. As far as I see we co

Re: ANN: Alpha release of new MS SQL Server backend

hey, sorry, forgot one thing: in django/db/models/fields 222 # mssql can not handle more than two 99-s 223 return ['%s-01-01 00:00:00' % value, '%s-12-31 23:59:59.99' % value] On Aug 3, 6:34 pm, mamcx <[EMAIL PROTECTED]> wrote: > Excelent. Please send me your patch so I

Re: ANN: Alpha release of new MS SQL Server backend

4, 9:21 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 8/3/07, pk11 <[EMAIL PROTECTED]> wrote: > > > the issue with object_id is that mssql can not insert an integer PK > > into a TEXT field. > > I guess I'm confused. Admin LogEntryManager fo

Re: schema evolution [testers wanted]

hey mike, we use a modified version of dbmigration in production at work, I sent you an email with our mods. cheers, peter > This part of the plan looks quite similar to the dbmigration project > athttp://www.aswmc.com/dbmigration/- hope that its useful in some way :) > If not, ah well, it work

Re: ANN: Alpha release of new MS SQL Server backend

hey, i will be able to send you my patch on monday. the generic idea is to attach LIMIT as if the backend supported it and at query execution time replace it with TOP. OFFSET can be handled by nested queries but i did not have enough time to finish that. (i.e. http://groups.google.com/group/djan

Re: ANN: Alpha release of new MS SQL Server backend

wrote: > On 8/3/07, pk11 <[EMAIL PROTECTED]> wrote: > > > - django's admin log model object_id's type is changed from text to > > integer (is there a reason why object_id is declared as textfield?) > > object_id is whatever the arbitrary model's PK i

Re: ANN: Alpha release of new MS SQL Server backend

hey all, we are also using django with pymssql/mssql, in addition to your work, we changed: - django's admin log model object_id's type is changed from text to integer (is there a reason why object_id is declared as textfield?) - pymssql is changed to allow unicode strings - simulate limit with

Re: schema evolution

Hi all, Derek, nice job! does your solution support all of the db backends or just sqlite/mysql/postgres? (we use a hacked version of dbmigration (http://www.aswmc.com/ dbmigration/) at work - works like a charm.) Thanks, Peter On Jul 20, 11:22 am, Sebastian Macias <[EMAIL PROTECTED]> wrote: >

Re: db parameter impemtation

Hi all, Not to hijack the thread but I think Django indeed supports prepared statements if the underlying db-binding supports it. This is from cx_Oracle's doc (http://www.cxtools.net/default.aspx? nav=cxorlb): execute(statement, [parameters], **keywordParameters) Execute a statement

Re: SQLServer Updates?

Hi all, I have a semi-working* pymssql patch if anyone interested. *= everything is working except: OFFSET (which is tough problem for MS SQL server) and the dbshell option for the manager but i believe that does not work for ADO as well. The reason why I did not release it is because at the mo