Re: One last Ruby question for tonight - Regarding UUID type
От | Mike Christensen |
---|---|
Тема | Re: One last Ruby question for tonight - Regarding UUID type |
Дата | |
Msg-id | AANLkTimNTQPvNg2+HfNNsf6uceyAZ_tUhZr_Dc8K+536@mail.gmail.com обсуждение исходный текст |
Ответ на | One last Ruby question for tonight - Regarding UUID type (Mike Christensen <mike@kitchenpc.com>) |
Ответы |
Re: One last Ruby question for tonight - Regarding UUID type
|
Список | pgsql-general |
> My goal is to learn Ruby by porting one of my existing PG web > applications over to Rails.. However, my existing data heavily relies > on the UUID data type. I've noticed when I create a new model with > something like: > > guidtest name:string value:uuid > > And then do a rake:migrate, the CREATE TABLE that gets generated looks like: > > CREATE TABLE guidtests > ( > id serial NOT NULL, > "name" character varying(255), > created_at timestamp without time zone, > updated_at timestamp without time zone, > CONSTRAINT guidtests_pkey PRIMARY KEY (id) > ) > ... > > In other words, it just ignores my "uuid" type. However, the views > and stuff do include this column so the page will crash when I load it > since the column doesn't exist in the DB. > Is there some special thing I have to do to use the uuid type in > ActiveRecord? Thanks! Update: If I manually add the column in using pgAdmin (as a uuid type of course), the program actually runs (I can create new rows and display data).. So RoR does support this type (probably gets marshalled as a string??) but I guess the ActiveRecord schema generation stuff just doesn't support uuid. Hmmm.
В списке pgsql-general по дате отправления: