Bug fixes and a new behavior to help catch potentially dangerous queries.
New Rose::DB is required, and it has some new features for dumping
registered data sources.
Files sent to CPAN and on SF.net:
http://sourceforge.net/project/showfiles.php?group_id=147570
Release notes below.
-John
0.755
On 10/20/06 3:05 PM, Ask Bjørn Hansen wrote:
> We (well, Graham) made the following manager class that gives us
> "fetch" and "fetch_or_create" methods to shorten the ->new(...)->load
> stuff and to factor out the speculative option logic.
On the object side of things (as opposed to the Manager) k
On 10/20/06 2:58 PM, Jonathan Vanasco wrote:
> I just wanted to bench the difference...
>
> auto_prime_caches is a class method, can't seem to find a way to
> toggle it globally
The "real" way to do it "globally" would be to make a custom metadata
subclass and set the auto_prime_caches attribute
On Oct 20, 2006, at 5:39 AM, John Siracusa wrote:
[...]
> If you know the class name already, just do this:
>
> $record = $class->new(primarykeyfieldname => $pk)->load;
We (well, Graham) made the following manager class that gives us
"fetch" and "fetch_or_create" methods to shorten the ->n
I just wanted to bench the difference...
auto_prime_caches is a class method, can't seem to find a way to
toggle it globally
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quick
Thanks again. I'm used to much less concise code - it's almost too easy!
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of John
> Siracusa
> Sent: 20 October 2006 13:40
> To: Rose-DB-Object
> Subject: Re: [RDBO] Elegant way to generically query a table?
On 10/20/06 2:37 AM, James Masters wrote:
> This is all working wonderfully. But now I want to do a similar thing with
> an individual record for which I know the primary key value. I assume it's
> quickest/best to use Rose::DB::Object rather than Manager in this case. But
> I can't see in the do
