From: Raphael Bauduin <raphael.bauduin@...>
Date: 2004-06-09T23:08:39+09:00
Subject: Re: [ANN] Active Record 0.8.3: Modules, mapping, and transactions

David Heinemeier Hansson wrote:
> What's new in Active Record 0.8.3?
> ==================================
> 
> Active Records in modules are now treated nicely by both the mapping  
> and association logic. The mapping can be more finely controlled with  
> options for different primary keys than �id� and for non-integer keys.  
> The dependent option on associations are now treated as a transaction.  
> And many other changes:
> 
> 
> Transactions
> ------------
> 
> * Added transactional protection for destroy
>   (important for the new :dependent option) [Suggested by Carl  Youngblood]
> 
> * Fixed so transactions are ignored on MyISAM tables for MySQL
>   (use InnoDB to get transactions)
> 
> * Changed transactions so only exceptions will cause a rollback, not  
> returned false.
> 
> 
> Mapping
> -------
> 
> * Added support for non-integer primary keys [Aredridel/earlier work by  
> Michael Neumann]
> 
>     User.find "jdoe"
>     Product.find "PDKEY-INT-12"
> 
> * Added option to specify naming method for primary key column.
>   ActiveRecord::Base.primary_key_prefix_type can either  be set to nil,  
> :table_name, or
>   :table_name_with_underscore. :table_name will assume that Product  
> class has a primary key
>   of "productid" and :table_name_with_underscore will assume  "product_id".
>   The default nil will just give "id".
> 


Hi,

Just tested it. It works find when you want only on object return, but fails when you do this:

ua = User.find(8,9,10)

The cause, from the output I got, is that the field used to order the returned rows is still name 'id'

Raph