Corrected a bad skip count that caused 0.7663 to appear to fail one of
its tests, and added a small fix and a small feature.
0.7664 (02.06.2008) - John Siracusa [EMAIL PROTECTED]
* Fixed a bug that caused boolean columns to be incorrectly marked as
modified. (Reported by Grzegorz
On Tue, Feb 05, 2008 at 07:04:10PM -0500, John Siracusa wrote:
On Feb 5, 2008 5:16 PM, Grzegorz Nosek [EMAIL PROTECTED] wrote:
Hmm, I might be missing something, but inside the
sql_qualify_columns_on_load method you're using $_[1] after shifting
$self off the argument array, so to set the
On Wed, Feb 06, 2008 at 08:29:49PM +0100, Grzegorz Nosek wrote:
Still, either I'm doing something very stupid, or the columns are now
always qualified, like this:
SELECT
t1.id,
t1.val1,
t1.val2,
t1.is_even
FROM
test t1
WHERE
t1.id = ? AND
t1.is_even = ? (2, 1)
brown
Hey all. I'm working on migrating a Class::DBI system to RDBO and I'm
wondering how to implement temp columns. In CDBI these are accessors that
behave like normal column accessors but don't store data in the database.
Weird, but sometimes useful. Here's how they're setup in Class::DBI:
On Feb 6, 2008 3:18 PM, Sam Tregar [EMAIL PROTECTED] wrote:
Hey all. I'm working on migrating a Class::DBI system to RDBO and I'm
wondering how to implement temp columns. In CDBI these are accessors that
behave like normal column accessors but don't store data in the database.
Weird, but
So I'm trying to get Rose::DB::Object set up. I have my database
class. I have my tables. I have my base object class. I would like
to generate all of my specific classes.
Rose::DB::Object wants to have plural table names. I have singular
table names. But that is supposed to be
