I'm brand new to Django, looking to see if I should use it for some
things I'd like to do with an existing database. One problem I ran
into pretty quickly is that the database tables have columns with
embedded spaces in their names. inspectdb runs without error but the
code it generates has syntax errors. For example:
class Entrie(models.Model):
Entry ID = models.IntegerField(primary_key=True)
Entry = models.CharField(blank=True, unique=True, maxlength=150)
class Meta:
db_table = 'Entries'
has to be changed to:
class Entrie(models.Model):
EntryID = models.IntegerField(primary_key=True, db_column="Entry
ID")
Entry = models.CharField(blank=True, unique=True, maxlength=150)
class Meta:
db_table = 'Entries'
before it can be imported without error. Then things seem to work --
I've been able to retrieve some values, etc., but haven't done anything
real yet. I'm wondering though, if I'm going to hit bigger problems
down the road. So my questions:
1 - Should inspectdb be able to handle columns with spaces in their
names? Should I file a ticket for this? I looked around but didn't
see anything that appeared relevant. Or:
2 - Does inspectdb's failute to handle this situation imply my existing
DB is really not well suited to mixing in Django at this point? Am I
likely to hit more serious roadblocks further on? FWIW, besides the
spaces in the column names I don't think there's anything too weird
about this DB.
I'm also curious about:
3 - Why was the trailing 's' taken off of the table named "Entries" to
generate the class Entrie?
Thanks for any enlightenment,
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
-~----------~----~----~----~------~----~------~--~---
