On Tue, 30 Jan 2007, [ISO-8859-1] Ask Bj?rn Hansen wrote:
> (although I sometimes get tripped up by forgetting by how ->new->load
> needs unique keys).
Me too. Does new->load to be restricted to unique keys? Couldn't there
be a way to provide a query and call the manager under the hood to
find, s
On 2/1/07 1:14 PM, Mike Schilli wrote
> On Tue, 30 Jan 2007, [ISO-8859-1] Ask Bjørn Hansen wrote:
>> (although I sometimes get tripped up by forgetting by how ->new->load
>> needs unique keys).
>
> Me too. Does new->load to be restricted to unique keys?
Yes, because each object is linked to a sin
On Thu, 1 Feb 2007, John Siracusa wrote:
> I question the wisdom of not supplying a sort_by paramater, however.
You're right, in the general case, sort_by is essential, but often
times, the application knows that there's either exactly one matching
record in the database or none.
It's something
On 2/1/07 2:03 PM, Mike Schilli wrote:
> On Thu, 1 Feb 2007, John Siracusa wrote:
>> I question the wisdom of not supplying a sort_by paramater, however.
>
> You're right, in the general case, sort_by is essential, but often
> times, the application knows that there's either exactly one matching
>
On Thu, 1 Feb 2007, John Siracusa wrote:
> Maybe you should share that information with the database... :)
Ha :). I can think of 3 different scenarios:
1) Two columns of a table form a combined unique key, but neither
of them can be defined UNIQUE().
2) You have a "unique key" that spans sev
On 2/1/07 3:21 PM, Mike Schilli wrote:
> 1) Two columns of a table form a combined unique key, but neither
>of them can be defined UNIQUE().
Then you'd just define a unique key using those two columns:
SQL: UNIQUE(col1, col2),
RDBO: unique_key => [ 'col1', 'col2' ],
> 2) You have a
Hello RDBO list members!
I am currently in the midst of converting our internal applications
from using Class::DBI over to Rose::DB::Object. One of the first
problems I encountered was needing support for multiple databases. In
searching the list archives, I found a solution that was
On 2/1/07 4:03 PM, Chris Jacobson wrote:
> *{ 'Rose::DB::MySQL::supports_schema' } = sub { 1 };
>
> This suits my purposes for the time being, but it would be nice to see
> this feature included in a future release of Rose::DB::MySQL.
It likely will be.
> I should also say that I have not done
