From: srinivasan.anand@...
Date: 2007-11-30T21:29:07+09:00
Subject: Re: railroad-database problem

Hi,
	Thanks for the valuble help. I have anyhow solved the problem.
The problem was that, as I have correctly guessed the rails was
expecting a reportings table. But I need to tell the rails that
reportings is not a table, but only a connection. I did that by
including the line "self.abstract_class=>true" in the reportings.rb file
so that the rails does not expect a table out of it.

Thanks and Regards,
S. Anand.

-----Original Message-----
From: list-bounce@example.com [mailto:list-bounce@example.com] On Behalf
Of Ilan Berci
Sent: Friday, November 30, 2007 2:41 AM
To: ruby-talk ML
Subject: Re: railroad-database problem

unknown wrote:
> Hi all,
> 
>             I am facing with a new type of problem with railroad,
> explained below
> 
> 
> 
> 1.                   I am using an oracle database in my application.
In
> the database.yml file, I am having different schema connections to the
> same database.like
> 
> 
> 
A database can only have one schema definition from a rails perspective.

From the configuration file it appears that you are attempting to have 
different users access the same db with different privilege sets. If 
this is the case, then make sure that both users can see the "Reporting"

table.

Secondly, as suggested earlier, you should check the console to make 
sure that you indeed have a table named: "reportings"..

Lastly, please post rails or "railroad" related questions to the rails 
forum.

hth

ilan



-- 
Posted via http://www.ruby-forum.com/.



This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.