I am just learning migrations and this was a test case. Although I read that PG 
documentation that suggests that there is no difference between a varchar(n) 
and text type.

How can I use table.newColumn for a boolean type column? if I use 
newBooleanColumn, it is creating an int type column. PG creates a boolean that 
return t or f.


create table testtbl (id int, mybool boolean);

insert into testtbl (id, mybool) values (1, 'YES');

psql testtbl

mytest=# \d testtbl    

Table "public.testtbl"

 Column |  Type   | Modifiers 
--------+---------+-----------
 id     | integer | 
 mybool | boolean | 

mytest=# select * from testtbl;                                                 
                                                                                
      id | mybool 
----+--------
  1 | t
(1 row)


I guess I could just use the varchar(5) column and use the kludge for inserting 
true and false.


Ted



> Message: 10
> Date: Tue, 1 Jul 2008 12:28:48 -0400
> From: Mike Schrag <[EMAIL PROTECTED]>
> Subject: Re: postgresql and 'text' prototype
> To: webobjects-dev Apple <[email protected]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset="us-ascii"
> 
> > 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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to