Non-conventional table name support for Postgres provider

[JejoSwaks]

Non conventional Postgres table name support

I know we all should stick to what the manpages tell us: use [a-z] (and maybe some other tokens such as _) when choosing table names. However, in some cases - i.e. legacy support; data migrations ... usage of reserved keywords .. unicode language tokens ... hard-headed devs that love their casing, it is desirable to go with something exotic. The library currently assumes tables follow the "correct" naming convention and omits double quotes

Would be nice-to-have if, for instance,

• The library uses double quotes
• Detects non-conventional table names and uses quotes when deemed necessary.

For a project of mine, I took the liberty to add quotes wherever needed. If you agree, I'll fire away a PR if you like.

[jonwagner]

My guess is that it currently supports quotes sometimes, but not consistently. If you have a PR to support quotes, send it along!

[jonwagner]

Let me know if you have more info on this. I can put it into an upcoming build.