> Is this a known bug:
> querying with primary keys ignores conditions for other fields
> ?
No, that's really a feature. Since a primary key has to be unique (otherwise
it isn't a primary key), it's the only thing you need to find a record (at
least if you compare with equality). So there is no need to pass all the
other fields to the where expression. This is an optimazation for the case
where you pass a hash with a bunch of fieldnames. In this way only the
necessary one gets to the SQL engine.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
