On 6/1/07, Matthew K. Williams <[EMAIL PROTECTED]> wrote: > Any idea where I could begin to look to see why mysql handles the > association tables for habtm differently than, say, hsqldb? > > If I have the following tables. projects and contacts, and there exists > a habtm relationship between contacts and projects, then ActiveRecord > creates the contacts_projects table for me automagickally for mysql, but > it's not doing it for hsqldb. > > I'd like to fix this behaviour......
Really? Where do you observe this? AFAICT Rails requires you to create all tables, including association tables. create_table :exercises_types, :id => false do |t| t.column "exercise_id", :integer t.column "type_id", :integer end /Nick _______________________________________________ Jruby-extras-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/jruby-extras-devel
