Changeset 18513 for ext

Show
Ignore:
Timestamp:
10/20/07 23:43:36 (15 months ago)
Author:
Darren_Duncan
Message:

ext/Muldis-DB/ : removed the files Operators.pm and PhysType?.pm but they will be replaced later

Location:
ext/Muldis-DB
Files:
1 removed
5 modified

Legend:

Unmodified
Added
Removed

  • ext/Muldis-DB/Changes

    r18396 r18513  
    1010    which sets its own less frequent release schedule.  The rest of this 
    1111    Changes entry refers only to the Perl 5 version. 
     12 
     13    * Removed the files PhysType.pm and Operators.pm; these files were very 
     14    out of date and will be replaced later (possibly under the same names). 
    1215 
    1316    * New file versions are: DB.pm and Interface.pm and Validator.pm and 
    … …  
    2831    exp_ast_lang, which will be maintained in future releases at the latest 
    2932    official Muldis D version number known to work at the time. 
     33 
     34    * (DB.pm)  Some small DESCRIPTION pod updates. 
     35 
     36    * (SeeAlso.pod)  Added more prospective extension modules. 
    3037 
    3138    * Fleshed out the tail of this Changes file with a summary pre-release 

  • ext/Muldis-DB/lib/Muldis/DB.pm

    r18105 r18513  
    7373these components make it possible for the Muldis DB core distribution to be 
    7474completely testable on its own.  It is therefore also feasible for an 
    75 application to use Muldis DB in isolation from further framework 
     75application to use the Muldis DB core in isolation from further framework 
    7676components, though doing so isn't recommended for production use since 
    7777C<Example> is kept simple on purpose and doesn't scale well. 
    … …  
    136136 
    137137One distinctive feature of a Muldis DB DBMS (compared to a typical other 
    138 vendor's DBMS) is that data definition statements are structured as 
    139 standard data manipulation statements but that the target relation 
    140 variables are system catalog relation variables rather than user-defined 
    141 relation variables.  In SQL terms, you create or alter tables by adding or 
    142 updating their "information schema" records, which in SQL are read-only, 
    143 not by using special 'create' or 'alter' statements. 
     138vendor's DBMS) is that data definition statements are structured 
     139fundamentally as standard data manipulation statements but that the target 
     140relation variables are system catalog relation variables rather than 
     141user-defined relation variables.  In SQL terms, you create or alter tables 
     142by adding or updating their "information schema" records, which in SQL are 
     143read-only, not only by using special 'create' or 'alter' statements. 
    144144 
    145145Each Muldis DB Engine has the complete freedom to implement the Muldis DB 
    … …  
    169169Independence>.  To further demonstrate the difference, it is useful to 
    170170compare the DBI and Muldis DB.  I<Such documentation is currently absent.> 
     171 
     172In the context of a Muldis DB implementation over the Perl DBI, if one were 
     173to categorize Muldis DB among other Perl modules, it could reasonably be 
     174called a database abstraction layer; but it should I<not> be called a Perl 
     175object persistence layer, as that is a different paradigm. 
    171176 
    172177=head1 FEATURE SUPPORT VALIDATION 

  • ext/Muldis-DB/lib/Muldis/DB/Engine/Example.pm

    r18252 r18513  
    22 
    33use Muldis::DB::Interface; 
    4 use Muldis::DB::Engine::Example::Operators; 
    54 
    65########################################################################### 

  • ext/Muldis-DB/lib/Muldis/DB/SeeAlso.pod

    r18105 r18513  
    178178which results in Muldis DB being an alternative API for them. 
    179179 
     180=item C<Muldis::DB::Engine::DBI> 
     181 
     182A Muldis DB Engine built around the Perl DBI module in a more generic 
     183fashion, that would work with multiple DBD modules rather than being 
     184specific to one SQL DBMS, could be named this. 
     185 
    180186=item C<DBIx::Class::Storage::MuldisDB> etc 
    181187 

  • ext/Muldis-DB/t/MDB_00_Compile.t

    r18105 r18513  
    33use Test; 
    44 
    5 plan( 12 ); 
     5plan( 8 ); 
    66 
    77use_ok( 'Muldis::DB' ); 
    … …  
    1717    'Muldis::DB::Validator is the correct version' );} ); 
    1818 
    19 use_ok( 'Muldis::DB::Engine::Example::PhysType' ); 
    20 skip( 1, q{is( Muldis::DB::Engine::Example::PhysType.WHO.version, 0.4.0, 
    21     'Muldis::DB::Engine::Example::PhysType is the correct version' );} ); 
    22  
    23 use_ok( 'Muldis::DB::Engine::Example::Operators' ); 
    24 skip( 1, q{is( Muldis::DB::Engine::Example::Operators.WHO.version, 0.4.0, 
    25     'Muldis::DB::Engine::Example::Operators is the correct version' );} ); 
    26  
    2719use_ok( 'Muldis::DB::Engine::Example' ); 
    2820skip( 1, q{is( Muldis::DB::Engine::Example.WHO.version, 0.4.0,