... and by the way ... also quoting from the link concerning performance
of char, varchar and text
Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type.
Why not simply replace all varchar types by text and be fine forever?
Carlos? What do you say? Other Postgres experts?
Cheers,
Oliver
Carlos Villegas wrote:
Oliver Zeigermann wrote:
This was fixed for *MySQL* only, *Postgres* still needs the fix.
Simple solution would be to increase the maximum size of the property.
Maybe there is something similar to "text" in MySQL in Postgres as well?
Yes, "TEXT" is supported in PostgreSQL:
http://www.postgresql.org/docs/7.4/interactive/datatype-character.html
Carlos
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
