Hi Jason, Welcome back!
On 1 May 2012 at 15:54, Richardson, Jason - FSA, Kans wrote: > Quick question, and some background info. > Sounds like a reasonable target.. .... snip ... > > Assignments > Assignments-dom > Assignments-fixture > Assignments-objstore-dflt > Assignments-tests-bdd > Assignments-tests-junit > Assignments-webapp > > > I am using PostgreSQL 9.1 for the database. > > In which project pom do I put in the PostgreSQL driver dependencies (does > anyone have an example for Postgresql 9.1? I would suggest adding it to the "Assignments-objstore-dflt", but as long as it is included in your deployed environment, you should be ok. > Which isis.properties file do I setup my Postgresql Datasource in? I assume > it's the Assignments-webapp Yes, sounds right. > ================================== > ================================== > Here is the Rails Schema, but its just a baseline that I'm to use as the > starting point for my ISIS Domain Objects. > Again, I'll use ISIS itself to actually create the tables. > > ======== Rails Scheme Begin ========= > > create_table "airports", :force => true do |t| > t.datetime "created_at" > t.datetime "updated_at" > end You should be safe with an appropriate naming convention. e.g. for the above, have an "airports" domain object, with members "createdAt", etc (e.g. getCreatedAt, setCreatedAt) > > create_table "assignments", :force => true do |t| > t.integer "worker_id" > t.integer "job_id" > t.datetime "_start" > t.datetime "_end" > t.datetime "created_at" > t.datetime "updated_at" > end You are going to run into issues if Ruby and Isis are to co-operate. In Isis, your "worker_id" will become "fk_worker" for a domain object called "worker". > create_table "workers", :force => true do |t| > t.integer "shift_id" > t.integer "user_id" > t.integer "position_id" > t.datetime "_start" > t.datetime "_end" > t.datetime "created_at" > t.datetime "updated_at" > end > > ======== Rails Scheme END ========= > Regards, Kevin
