The citext module provides a case-insensitive character string type, citext. Essentially, it internally calls lower when comparing values. Otherwise, it behaves almost exactly like text.
Personally, I think you are working too hard. are you planning on writing your own SQL? you can still use migrations because in a migration, you can issue your own SQL. do your migrations without the 'special' column, then add it with SQL (assuming you have added the citext module). ERXJDBCUtilities.executeUpdate(database.adaptorChannel(), "ALTER TABLE t_user ADD column myspecialcolumn citext"); On Nov 19, 2013, at 9:26 AM, Frank Stock <[email protected]> wrote: > Hi all, > > Is there a reason why you can't select citext to use instead of varchar in > the prototypes of the modeler (Postgresql)? > I can manual change the type in de database, but that I won't be able to use > ERMigration. > > Thanks, > Frank Stock > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
