[PERFORM] TEXT or LONGTEXT?
Hello, I have a database with an amount of tables and in several of them I have an attribute for a semantic definition, for which I use a field of type text. I am trying to decide if it would be worth using LONGTEXT instead of TEXT, as maybe it would slow down the data insertion and extraction. I hope that you could help me. Thank you. -- Fabiola Fernández Gutiérrez Grupo de Ingeniería Biomédica Escuela Superior de Ingeniería Camino de los Descubrimientos, s/n Isla de la Cartuja 41092 Sevilla (Spain) Tfno: +34 954487399 E-mail: [EMAIL PROTECTED]
Re: [PERFORM] TEXT or LONGTEXT?
On 9/24/07, Fabiola Fernández [EMAIL PROTECTED] wrote: I have a database with an amount of tables and in several of them I have an attribute for a semantic definition, for which I use a field of type text. I am trying to decide if it would be worth using LONGTEXT instead of TEXT, as maybe it would slow down the data insertion and extraction. I hope that you could help me. Thank you. Easy choice -- PostgreSQL does not have a data type named longtext. Alexander. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [PERFORM] TEXT or LONGTEXT?
On 24 sep 2007, at 17.21, Fabiola Fernández wrote: I am trying to decide if it would be worth using LONGTEXT instead of TEXT, as maybe it would slow down the data insertion and extraction. Postgres doesn't have a LONGTEXT datatype, so keep using TEXT. http://www.postgresql.org/docs/8.2/interactive/datatype-character.html Sincerely, Niklas Johansson ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
