Thanks for the response - looks like I am going to have to bite the
bullet and get on with it. From a Rails perspective, these databases are
a mess, in fact from a SQL Server perspective they are a mess and the
company knows it, what they won''t do is use some resource to clean them
up.
>From some initial testing, the framework seems to be ignoring the
set_primary_key setting that I have provided for the test table, but
maybe I have set the query up wrong or something - will go back and
check.
Best get the waders on.
Clive
On Wed, 2007-08-29 at 04:36 +0000, Rich C wrote:
> I would just create models for each table (script/generate model
> table_name), then get real familiar with
''set_table_name'', and
> ''set_primary_key''. If they are using compound primary
keys, then
> you''ll need Dr Nic''s
''CompoundPrimaryKey'' gem.
>
> I''d also recommend creating the associations manually and not
using
> the ''magic models'' plugin.
>
> I''ve done it with our in-house SQL Server db''s and it
works fine...
>
> Good Luck,
>
> Rich C.
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
