On 8/22/06 7:56 PM, Randal L. Schwartz wrote:
>> "John" == John Siracusa <[EMAIL PROTECTED]> writes:
>
> John> The last release (0.75) included this change:
>
> Hopefully *not* the last release. I'm hoping you mean "latest" or "most
> recent", and not final. :)
Yes, the prior, the preceding, th
> "John" == John Siracusa <[EMAIL PROTECTED]> writes:
John> The last release (0.75) included this change:
Hopefully *not* the last release. I'm hoping you mean "latest" or "most
recent", and not final. :)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
http
On 8/22/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> if abcdefg is not a real 'column' ( / getset method on the rose db
> object ), it is just silently ignored
>
> shouldn't that throw an error ? rose is otherwise very strict , and
> keeps people from making silly mistakes like that.
The las
On Aug 22, 2006, at 11:46 AM, John Siracusa wrote:
> Methods that say they fetch stuff form the DB actually do what they
> say, with no caching. Rose::DB::Object::Cached changes load() to pull
> from a cache instead of the db. But even then, there are ways to
> override this behavior and/or cle
i just noticed this:
eval {
# first we fetch the other objects
$results= $class->get_objects(
query=> [
id=> $kw_args{'id'},
abcdefg=> $kw_args{'abcdefg'},
On 8/22/06, Jonathan Vanasco <[EMAIL PROTECTED]> wrote:
> do i need to do anything to not have rose internally cache stuff, or
> periodically clear it out? or is caching only used when items are
> inherited from Rose::DB::Object::Cached ?
>
> I seem to remember something about caching on loads/sav
just wondering-
do i need to do anything to not have rose internally cache stuff, or
periodically clear it out? or is caching only used when items are
inherited from Rose::DB::Object::Cached ?
I seem to remember something about caching on loads/saves.
---