r6414@wilber: samv | 2006-03-29 17:15:20 +1200

 Sync with 2.09 release.

Changes.pod

@@ -1,14 +1,25 @@
 
 =head1 WHAT'S NEW IN TANGRAM
 
-=head1 RELEASE 2.10, xxx 2005
+=head1 RELEASE 2.10, 29 Mar 2006
 
 This release is the first step in the major refactoring of Tangram,
 which is API-backwards compatible.  The differences between 2.09 and
 2.10 are limited to namespace re-organisation.  The test suite still
 succeeds unmodified, but has been tweaked to suppress warnings that
 deprecated modules are being used.
 
+=over
+
+=item *
+
+Sync release with 2.09.  svk this time made this extremely painful,
+but we must forgive it because after all trying to support distributed
+source management tool atop of a synchronised versioning filesystem is
+pushing shit uphill.
+
+=back
+
 =head2 DEV. RELEASE 2.09_02, 21 Nov 2005
 
 =over
@@ -42,10 +53,20 @@ C<:compat_quiet>.  to be documented.
 
 =back
 
-=head1 RELEASE 2.09, slated for October 2005
+=head1 RELEASE 2.09, 29 Mar 2006
+
+=over
+
+=item *
+
+Disable some tests on MySQL, that try to do things far too difficult
+for its little brain.
 
-Unless more critical bugs are reported, the latest 2.08_XX release
-will be released as 2.09 in August^WSeptember^WOctober^WRSN!
+=item *
+
+Suppress a warning in the test suite.
+
+=back
 
 =head2 DEV. RELEASE 2.08_06, 21 Nov 2005
 

lib/Tangram.pm

@@ -15,7 +15,7 @@ require Exporter;
 );
 
 { local($^W) = 0;
-$VERSION = '2.09_02';
+$VERSION = '2.10';
 my $force_numeric = $VERSION + 0;
 }
 

lib/Tangram/Storage.pod

@@ -443,9 +443,12 @@ objects.  These tables are joined with an outer join clause.
 
 The outer join related code is extremely hairy, and you are advised to
 ensure that you test each outer join query that you are going to use
-with new versions of Tangram.  In particular, having classes in the
-outer section of a join which involve more than two underlying tables
-is currently TODO.
+with new versions of Tangram.
+
+Do not try to combine inheritance and outer joins if you want to run
+your application on toy databases, currently this means SQLite and
+MySQL.  SQLite does not parse SQL nested join syntax and MySQL just
+gets the join all wrong.  At least, on my testbed system.  YMMV.
 
 =head2 sum( $expr, [$filter] )
 

metatest.pl

@@ -2,7 +2,9 @@
 
 use strict;
 
-@ARGV = qw( SQLite myisam innodb Pg Oracle ) unless @ARGV;
+# note to the observant - this list represents the lists of RDBMSes
+# the maintainer is hopefully testing releases on :-)
+@ARGV = qw( SQLite SQLite2 myisam innodb Pg ) unless @ARGV;
 
 delete $ENV{LANG};
 

t/misc/new_opers.t

@@ -43,9 +43,9 @@ $output->capture_print();
 
 my @cp = ($db_cs, $DBConfig::user, $DBConfig::passwd);
 
-my $dbh = DBI->connect( @cp )
+my $dbh = DBI->connect( @cp, { PrintError => 0 } )
     or skip "could not connect to database", 1;
-eval { Tangram::Relational->retreat($schema, $dbh) };
+eval { Tangram::Relational->retreat($schema, $dbh, { PrintError => 0 }) };
 eval { Tangram::Relational->deploy($schema, $dbh) };
 is( $@, "", "Fascists deployed!" );
 my $result = $output->release_stdout();

t/springfield/03-queries.t

@@ -127,6 +127,12 @@ SKIP:{
    skip "SQLite can't do nested joins", 1
        if DBConfig->dialect =~ /sqlite/i;
 
+   skip "MySQL known to return incorrect results for nested joins", 1
+       if DBConfig->dialect =~ /mysql/i;
+
+   skip "MySQL known to return incorrect results for nested joins", 1
+       if DBConfig->dialect =~ /mysql/i;
+
 # first, setup some test data
 {
    my $storage = Springfield::connect(undef, { dbh => $dbh });