On 7/11/07, Carl Karsten <[EMAIL PROTECTED]> wrote: > What is djagoo's approach to passing values to the back end: > > A) create a string that is the SQL command and the values, pass that string to > the db module. > > B) create a string that is the SQL command with parameter markers, pass that > string and the values to the db module.
This sounds like a strange way to ask if Django is using prepared statements[1] or their equivalents, rather than simply supplying values directly within the SQL statement itself. To my knowledge, Django doesn't support them, and I haven't heard anything about existing code being intended to support them. I suppose whether it'd be a good idea in the future would be a question for future debate, but I don't think there's any reason to file a bug about the current behavior. -Gul [1] http://dev.mysql.com/tech-resources/articles/4.1/prepared-statements.html --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
