hi Michael, Thanks for your response! One more question, see below.
Op dinsdag 10 juli 2012 17:51:16 UTC+2 schreef Michael Manfre het volgende: > > I haven't tested your patch or backend and only have a few comments on > implementation ideas for a custom database backend. > > [...] > > >> * No support for != operation (only <>). >> > > You'll need to provide your own SQLCompiler and do the substitution there. > You can look at django-mssql's implementation [1] as an example. > But the test script has != hardcoded in it, is it the idea that you scan every query for such character combination? Isn't this bad practice since it will have a performance impact since it is performed on all queries? > > [1] > https://bitbucket.org/Manfre/django-mssql/src/eff1ed275fdd/sqlserver_ado/compiler.py > > > Regards, > Michael Manfre > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/7NfavbkROYgJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
