RoR with Existing tables in database using Postgresql
PalaniKannan K
I am new bee to Rais. I need to create a Rails application with existing database with several number of tables. When i came across web, I didn't find any fruitful ideas for developing application using existing tables. Everything i found was to create new database with Create, Edit, Insert feature. I need to create a application using existing postgresql database stuffed with tables where i have to provide view only permission to the user. Kinldy help me in this regard. I have 15 tables in my database which developed in postgresql. Advance thanx to my friends of RoR-Talk.
--
Palani Kannan. K
Kannan
Ar Chron
Providing only 'read access' simply means your rails application should
not accept any new/create/update requests, and there are numerous ways
to defend against this.
--
Posted via http://www.ruby-forum.com/.
Richard Henwood
Hi Palani,
you might find this helpful:
http://www.theirishpenguin.com/2009/11/26/generate-rails-migrations-from-
your-postgresql-or-mysql-database/
richard,
PalaniKannan K
Start with googling 'rails legacy database' for ideas.
Yaa... I will use this hint. Thank You.
Providing only 'read access' simply means your rails application should
not accept any new/create/update requests, and there are numerous ways
to defend against this.
Can you please tell me the ways... It will be useful to me. Tanx advance.
--
Posted via http://www.ruby-forum.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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
--
PalaniKannan K
Hi Palani,On Fri, 03 Sep 2010 12:16:26 +0200, PalaniKannan K wrote:
> Hi,
>
> I am new bee to Rais. I need to create a Rails application with existing
> database with several number of tables. When i came across web, I didn't
> find any fruitful ideas for developing application using existing
> tables. Everything i found was to create new database with Create, Edit,
> Insert feature. I need to create a application using existing postgresql
> database stuffed with tables where i have to provide view only
> permission to the user. Kinldy help me in this regard. I have 15 tables
> in my database which developed in postgresql. Advance thanx to my
> friends of RoR-Talk. --
you might find this helpful:
I feel that, this is same kind of results I got in google search... Creating model using dumped schemas of existing table. but, its not working.
http://www.theirishpenguin.com/2009/11/26/generate-rails-migrations-from-
your-postgresql-or-mysql-database/
richard,
--
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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hassan Schroeder
> I feel that, this is same kind of results I got in google search... Creating
> model using dumped schemas of existing table. but, its not working.
"its not working" isn't particularly useful information.
So you have an existing table, say "things". You create a model for
it, e.g.
class Thing < ActiveRecord::Base
end
Done. Maybe you have to tell it there's a non-Rails-standard index
field, etc., but basically that's it. There's no reason to be fooling with
migrations if you have an existing table, unless you can and want to
do transformations on them to make them more Rails-like.
So what have you tried, and what's the actual problem?
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
PalaniKannan K
On Fri, Sep 3, 2010 at 8:59 AM, PalaniKannan K <kpalan...@gmail.com> wrote:"its not working" isn't particularly useful information.
> I feel that, this is same kind of results I got in google search... Creating
> model using dumped schemas of existing table. but, its not working.
So you have an existing table, say "things". You create a model for
it, e.g.
class Thing < ActiveRecord::Base
end
Done. Maybe you have to tell it there's a non-Rails-standard index
field, etc., but basically that's it. There's no reason to be fooling with
migrations if you have an existing table, unless you can and want to
do transformations on them to make them more Rails-like.
Realy Sorry... If my problem was not understandable. I am a new bee... there is no perfect tutorials available for already existing tables to develop web interface. In before cases I used cgi and perl. Now I started ruby and RoR. I feel its totally different from cgi. If you know any turorials with examples, kindly tell me. In previously mentioned link, I am unable to understand.
So what have you tried, and what's the actual problem?
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
--
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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hassan Schroeder
> Realy Sorry... If my problem was not understandable. I am a new bee... there
> is no perfect tutorials available for already existing tables to develop web
> interface. In before cases I used cgi and perl. Now I started ruby and RoR.
> I feel its totally different from cgi. If you know any turorials with
> examples, kindly tell me. In previously mentioned link, I am unable to
> understand.
The earlier link was irrelevant, ignore it. The advice to google "rails
legacy database" from Ar Chron should help, though.
In any case, make a copy of your existing DB and point your Rails
app at it.
Create a model based on an existing table e.g. "things", as in
class Thing < ActiveRecord::Base
end
Then start a console and type
thing = Thing.first
Look at the result. That should get you started :-)
And no, sorry, I don't know of any specific tutorials on doing this. It
would probably be easier if you'd already developed at least a trivial
green-field Rails app (gone through the basic tutorials, guides, etc.)
FWIW, and good luck,
E. Litwin
wrote:
>
> class Thing < ActiveRecord::Base
> end
>
legacy table is, unless it happens to be "id"
class Thing < ActiveRecord::Base
set_primary_key "[PKFieldName]"
end
Hassan Schroeder
> Odds are, you will need to tell Rails what the primary key of your
> legacy table is, unless it happens to be "id"
Absolutely, and odds are the OP will encounter other grief in the form
of naming conventions/pluralization yadda yadda. :-)
But creating a model and seeing what happens and where it breaks[*]
is the best way to start, IMO. And as a matter of fact I'm currently up
to my armpits in a similar project, though I do have the leeway to do
a few Railsizations to the db schema, thankfully.
[*] by writing tests, hopefully!
FWIW,
Cuz Ican
http://magicmodels.rubyforge.org/magic_model_generator/
http://github.com/ahe/reverse_scaffold
Also, read this forum to consider some potential messy things.
http://www.ruby-forum.com/topic/149050
PalaniKannan K
The Problem got solved... Thank you for valuable comments from each one in this thread.
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 rubyonra...@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-ta...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.