Thanks for the reply! It sort of turns out that the development (and anything generated from a "rake migrate" step) work as intended. However, it seems that the test database is created by running db/schema.rb, which has badness.
I know the general work of acriverecord is to maintain as much database agnostic types as it can, but this is contrary to my reality. I choose to use postgresql because it has these features, and not being able to use them in rails makes my coworkers question the use of rails, not the use of postgresql. I'll have to look into ways to contribute back I suppose, and see what happens. Types like t.reference would have to change to bigint in my world as well, or I'll have to create the othertable_id columns as bigint specially. --Michael On Thu, Jan 22, 2009 at 1:15 AM, Mark Reginald James <[email protected]> wrote: > > Michael Graff wrote: >> I am willing to give up the common denominator in database >> compatibility and dive into using some PostgreSQL specific types. In >> particular, I need bigint (int8) id columns and 'cidr' data type. > > Can't help you on the cidr, but to change the id to bigint I've used > > change_column :probes, :id, :bigint, :limit => 8 > > after the create_table block. > > -- > Rails Wheels - Find Plugins, List & Sell Plugins - http://railswheels.com > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
