better naming model tables

[lsloan]

If I let Django name the DB tables, it prefixes each one with the name of the app. For example, the table for the Assessment class gets named peer_review_data_assessment, which I don't like.

I don't understand why 3/8 of the programmatic table namings don't work. They required me to hard-code them. I'd like an alternate technique that gives better table names programmatically without the occasional unexplained error.

Originally posted by @ssciolla in #11 (comment):

After digging into the import situation a bit, it looks like you are defining db_table in many cases (not all) by using the internal name of the class from canvasapi. It's probably okay, but I guess I'd lean towards hard-coding the names, or letting Django generate them based on the class name, to avoid any possible downstream effects of changes in the library classes or structure.

[lsloan]

Code that seems close to working…

# Should this class be abstract?  Is base class correct?
class MyModelBase(models.base.ModelBase):
    def __new__(cls, name, bases, attrs, **kwargs):
        class NewMeta:
            db_table = name

        attrs['Meta'] = NewMeta

        r = super().__new__(cls, name, bases, attrs, **kwargs)
        return r


# Is the base class correct, or should it be models.base.Model?
class MyModel(models.Model, metaclass=MyModelBase):
    class Meta:
        abstract = True


class Course(MyModel):
    # etc.

However, this code gives the error…

django.core.exceptions.FieldError: Local field 'id' in class 'Course' clashes with field of the same name from base class 'MyModel'.

[ssciolla]

Can this be closed?