Skip to content
New issue

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

Option to import as text instead of varchar with specific size #21

Open
geraldodev opened this issue Sep 3, 2015 · 0 comments
Open

Comments

@geraldodev
Copy link

Use case:

Imported tables cannot be inherit from common table due to difference of varchar column length.

Tip from http://www.postgresql.org/docs/9.1/static/datatype-character.html

"There is no performance difference among these three types, apart from increased storage space when using the blank-padded type, and a few extra CPU cycles to check the length when storing into a length-constrained column. While character(n) has performance advantages in some other database systems, there is no such advantage in PostgreSQL; in fact character(n) is usually the slowest of the three because of its additional storage costs. In most situations text or character varying should be used instead."

spierg added a commit to spierg/pgdbf that referenced this issue Sep 4, 2015
Addressing issue kstrauser#21.
This change prevent errors when saving strings as  some accented characters take more than 1 byte to store in the database.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant