You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"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."
The text was updated successfully, but these errors were encountered:
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.
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."
The text was updated successfully, but these errors were encountered: