Manasi V1 wrote:> Hi..
> I have a similar system where my source db is legacy Oracle db. What I
> have done is use MySQL db for development and Oracle in other
> environments..You will need the schema for setting up local. Don''t
> import the db at one go.. Create migrations as you establish models and
> associations for the app..
> you can use SQL scripts if you want soem raw test data.
>
> Thanks
Actually this was just for learning purposes. I don''t really want to
sit and manually add entries in a browser -- I''d like a decent size
database to play with while I get used to API. So I''m writing a short
ruby script to collate some filesystem data into an sqlite3 file. Which
shouldn''t take much longer, hopefully everything will be okay. If not
I
will just pull the rails "development.sqlite3" file out and add to
that
(I guess that''s really what I should be doing...). I''m using
the same
fields as in the schema, plus "id", which AFAICT is just an int count
(1,2,3...).
So I was wondering if there are any caveats about this. (It''s a
pre-emptive post; the next one will be "Whhaaa...Why won''t the
database
I made work in rails?") ;)
MK
--
Posted via http://www.ruby-forum.com/.