We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
makes it really hard to import into Postgresql since "table" is a reserved name :/
The text was updated successfully, but these errors were encountered:
How about "Table_"? This is how Thomson Reuters resolves similar problems in its database products (we call them "Date_" etc.
Cezary
On Fri, Apr 25, 2014 at 4:23 PM, Brian Abelson [email protected]:
makes it really hard to import into Postgresql since "table" is a reserved name :/ — Reply to this email directly or view it on GitHubhttps://github.com//issues/201 .
— Reply to this email directly or view it on GitHubhttps://github.com//issues/201 .
Cezary Podkul | @cezary Mobile: (708) 228 1319 Web: cezarypodkul.com
Sorry, something went wrong.
You could alway put quote marks around the column names when importing to Postgresql.
abelsonlive
No branches or pull requests
makes it really hard to import into Postgresql since "table" is a reserved name :/
The text was updated successfully, but these errors were encountered: