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. >
This error is still occurring. I added some more logging information, but didn't get much, other than that this only happens with Timestamp, NOT Datetime, even though we use both of these frequently. What is the difference between Timestamp and Datetime, anyway? The corresponding Metadata/Column classes seem almost the same, with many of the minute differences seeming more accidental than anything else. 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
