Hi Malcolm, thanks for the quick (and encouraging) answer. >The only huge difficulty with making legacy (existing) databases work >with Django is when you have a multi-column primary key. We don't >support that yet (although it is planned).
Don't have any of those, so I'll plan to proceed investigating Django. >If you wanted to submit a patch to make it handle this automatically, we >would most likely accept it. Even if you don't feel like making a patch, >you could file a ticket, although it probably won't be fixed with high >priority -- but at least we won't forget to attend to it at some point. >(That sounds like I don't care about the problem, but it's more a matter >of there being things with a greater impact that can be dealt with >first. Inspectdb is a tool for a niche sector of our users and we can't >hope to get it perfectly right, so slight oddities are tolerated a >little more. However, we do aim to fix all genuine problems eventually, >if possible.) I understand completely. I was just a little worried that I could run into some big gotchas down the road with these oddball column names. The transformation required is pretty trivial, so perhaps I will look into making a patch. [She says blithely, having never glanced at a line of Python code before last night. But seriously, my favorite way to learn is to actually do something real, so it might be a good exercise for me.] >Inspectdb is trying to follow Django's normal pattern, but it chose >poorly. We suggest that model names be singular (since they represent a >single row in the table and a single instance of the thing you are >modelling) and this is converted to a plural form for the table name. Of >course, Django can't parse English, so some plural forms cause bad >guesses to be made. We just chop the trailing 's' off, nothing more >intelligent than that. Ah, I thought it might be something like that, but haven't actually gotten far enough along to appreciate why it was done. >You should feel free to rename your model class to whatever makes sense >(e.g. Entry). That is what you will use in Python and providing you have >things like db_table set as required, Django will handle the mapping >transparently. If you do rename your model to "Entry", you probably also >want to set the verbose_name_plural attribute in the Meta inner class so >that it still shows up as "Entries" in the right places in the admin >interface (otherwise you get to see "Entrys" and that is as odd as >"Entrie"). Thanks for that tip, I surely would have been looking around for how to fix "Entrys" when I got to that point also. I had actually changed Entrie to Entry when I edited the file, and just changed it back when posting to focus on the changes for the column name weirdness. Cheers, Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
