Handle invalid characters in table names

[danohu]

Fixes Issue #60

Also remove some unused duplicated code

[coveralls]

Coverage increased (+0.8%) to 90.83% when pulling 88a5ff9 on danohuiginn:invalid_table_name into 9667827 on agronholm:master.

[coveralls]

Coverage increased (+0.8%) to 90.83% when pulling 28571d1 on danohuiginn:invalid_table_name into 9667827 on agronholm:master.

[coveralls]

Coverage increased (+0.8%) to 90.83% when pulling 28571d1 on danohuiginn:invalid_table_name into 9667827 on agronholm:master.

[coveralls]

Coverage increased (+0.8%) to 90.83% when pulling 28571d1 on danohuiginn:invalid_table_name into 9667827 on agronholm:master.

[agronholm]

It's not obvious to me how this fixes anything.

[danohu]

hi @agronholm

so, you have a table called 'simple-items', as in the test case. Because there is no sanitization of table names, this will generate python code like:

class Simple-item(Base):

But you can't have a hyphen in a classname; it's interpreted as a minus sign, so you'll get a SyntaxError when importing the generated code. I assume (but haven't checked) that you'd get similar problems with other non-alphanumeric characters that are valid as db table names but have special meanings in python.

So I've passed table names through the existing sanitization routine, that converts non-alphanumeric characters into underscores.

[agronholm]

I see it now. Thanks!