Re: postgresql and 'text' prototype
Re: postgresql and 'text' prototype
- Subject: Re: postgresql and 'text' prototype
- From: Mike Schrag <email@hidden>
- Date: Tue, 1 Jul 2008 12:28:48 -0400
Using a StringColumn is not working.
You should use table.newColumn("c_firstname", java.sql.Types.LONGVARCHAR, 0, 0, 0, false, "");
Yeah, the newStringColumn will not work for this ... Basically it tries to guess which migration method it should use, and currently it's not able to guess this type. You can also try newClobColumn and see if that uses "text" -- not sure if there is a clob in pg, so it might default to that. But why are you using TEXT types for small text fields like firstname. Correct me if I'm wrong but I assume that you have much more performance and indexing power if you use varchar instead.
from pg manual: "Tip: There are no performance differences between these three types, apart from the increased storage size when using the blank-padded type. While character(n) has performance advantages in some other database systems, it has no such advantages in PostgreSQL. In most situations text or character varying should be used instead."
ms |
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden