On Oct 30, 2007, at 7:54 AM, John Siracusa wrote: > On 10/30/07, Jonathan Swartz <[EMAIL PROTECTED]> wrote: >> $column is a Rose::DB::Object::Metadata::Column::Timestamp, according >> to the error. The errors originate from all sorts of operations, but >> they always end in the exact error message above - it is always >> Timestamp. >> >> I can try loading Timestamp explicitly. But it sort of defies logic - >> if Timestamp weren't loaded, how would it know that Timestamp is an >> overloaded package? (Timestamp has no overloading of its own, it >> inherits it indirectly from Column). > > Yes, it doesn't make much sense, but not much about the > overload-related bugs I've seen does :-/ Can you edit QueryBuilder.pm > to see if you can at least work around it? For example, use > $column->name ne $method instead of relying on $column's overloaded "" > operator. If that works, I can change the code. >
I've edited QueryBuilder.pm to spew a variety of things into the logs if it looks like the error is about to happen. Changing the operation as you suggest would probably work, but I wouldn't mind knowing what's behind this... Jon ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
