One clarification I noticed just after hitting "send"... On Tue, 2006-09-19 at 13:44 +1000, Malcolm Tredinnick wrote: > On Tue, 2006-09-19 at 03:18 +0000, world_domination_kites wrote: [...] > > Am I right to think that "quote_name" should have responsability for > > knowing what constraint/table/column name to use. > > No, it shouldn't. All that function does is turn a string (which could > be a table name or column name) into something that can be passed to the > database. It is not given any context for that, just the string to > convert. At the moment, it pretty much just wraps quotes around things > in case there are spaces in the names.
I just wanted to clarify that the tricky part here is that quote_name does not know *what* it is quoting -- whether it's a table name, constraint name or column name. That's what I mean by no context being given. So whilst it wouldn't be impossible to set up quote_name to map each string onto a legal alternative for Oracle, you would also have to map the string "foo" onto the same resulting string, regardless of its function in the database. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. 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 -~----------~----~----~----~------~----~------~--~---
