Sijo k g wrote:
> Hi Vishnu
>
>In the normal case the procedure is like
>
> create_table :sales_orders, :id => false do |t|
> t.integer :ordernumber, :primary => true
>
> end
>
> Now in the class SalesOrder you can define like
> set_primary_key "ordernumber"
>And also you have
is practice.
>
> Best regards,
> Sebastian
>
> On Oct 31, 4:15�pm, Vishnu First
Sebastian,
Thank you for your reply. Its right to keep "ID" as primary key. But, my
client requirement is to keep the "ordernumber" as primary key. So, I am
hi,
I am doing unit testing. I have a table as SalesOrder, where
"ordernumber" is the primary key of the table. When I insert records in
the table from unit testing, I got error like,
ActiveRecord::RecordNotFound: Couldn't find SalesOrder without an ID
But, I have fixed the error by adding set
Hi,
I have project in Ruby as version 1.8.7. I am trying to use
Crusiecontrol.rb to build the project. But, when I saw in the
Cruisecontrol.rb documentation, in the prerequisite section, I found
that, the Cruisecontrol is build in Ruby 1.8.6. It does not work on Ruby
1.8.7 or 1.8.9. As I told, I
4 matches
Mail list logo