Permalink
Browse files

Trailing WS crusade - got to save them bits

  • Loading branch information...
ribasushi committed Jan 5, 2012
1 parent 33eafbf commit 8273e845426f0187b4ad6c4a1b42286fa09a648f
Showing with 504 additions and 524 deletions.
  1. +3 −0 Changes
  2. +1 −1 lib/DBIx/Class/Admin/Usage.pm
  3. +2 −2 lib/DBIx/Class/CDBICompat.pm
  4. +4 −4 lib/DBIx/Class/CDBICompat/AccessorMapping.pm
  5. +1 −1 lib/DBIx/Class/CDBICompat/LazyLoading.pm
  6. +2 −2 lib/DBIx/Class/DB.pm
  7. +7 −7 lib/DBIx/Class/InflateColumn/File.pm
  8. +4 −4 lib/DBIx/Class/Manual.pod
  9. +15 −15 lib/DBIx/Class/Manual/FAQ.pod
  10. +1 −1 lib/DBIx/Class/Manual/Glossary.pod
  11. +1 −1 lib/DBIx/Class/Manual/Intro.pod
  12. +5 −5 lib/DBIx/Class/Manual/Joining.pod
  13. +1 −1 lib/DBIx/Class/Manual/Reading.pod
  14. +6 −6 lib/DBIx/Class/Manual/Troubleshooting.pod
  15. +7 −7 lib/DBIx/Class/Optional/Dependencies.pm
  16. +25 −25 lib/DBIx/Class/Ordered.pm
  17. +20 −20 lib/DBIx/Class/Relationship.pm
  18. +1 −1 lib/DBIx/Class/Relationship/Accessor.pm
  19. +1 −1 lib/DBIx/Class/Relationship/Base.pm
  20. +1 −1 lib/DBIx/Class/Relationship/CascadeActions.pm
  21. +1 −1 lib/DBIx/Class/Relationship/ProxyMethods.pm
  22. +3 −3 lib/DBIx/Class/ResultClass/HashRefInflator.pm
  23. +3 −3 lib/DBIx/Class/ResultSet.pm
  24. +4 −4 lib/DBIx/Class/ResultSetColumn.pm
  25. +2 −2 lib/DBIx/Class/ResultSource/View.pm
  26. +1 −1 lib/DBIx/Class/ResultSourceHandle.pm
  27. +1 −1 lib/DBIx/Class/SQLMaker/LimitDialects.pm
  28. +3 −3 lib/DBIx/Class/Storage/DBI.pm
  29. +2 −2 lib/DBIx/Class/Storage/DBI/MultiColumnIn.pm
  30. +1 −1 lib/DBIx/Class/Storage/DBI/ODBC/SQL_Anywhere.pm
  31. +1 −1 lib/DBIx/Class/Storage/DBI/Oracle/Generic.pm
  32. +9 −9 lib/DBIx/Class/Storage/DBI/Replicated/Balancer.pm
  33. +8 −8 lib/DBIx/Class/Storage/DBI/Replicated/Introduction.pod
  34. +7 −7 lib/DBIx/Class/Storage/DBI/Replicated/Pool.pm
  35. +1 −1 lib/DBIx/Class/Storage/DBI/SQLite.pm
  36. +1 −1 lib/DBIx/Class/Storage/DBI/Sybase/Microsoft_SQL_Server.pm
  37. +1 −1 lib/DBIx/Class/Storage/DBI/mysql.pm
  38. +2 −2 lib/DBIx/Class/Storage/DBIHacks.pm
  39. +1 −1 lib/DBIx/Class/UTF8Columns.pm
  40. +38 −38 t/101populate_rs.t
  41. +2 −2 t/103many_to_many_warning.t
  42. +2 −2 t/105view_deps.t
  43. +1 −1 t/39load_namespaces_rt41083.t
  44. +1 −1 t/53lean_startup.t
  45. +3 −3 t/60core.t
  46. +1 −1 t/63register_class.t
  47. +1 −1 t/63register_column.t
  48. +1 −1 t/64db.t
  49. +1 −1 t/65multipk.t
  50. +1 −1 t/67pager.t
  51. +1 −1 t/69update.t
  52. +1 −1 t/70auto.t
  53. +3 −3 t/71mysql.t
  54. +1 −1 t/72pg.t
  55. +1 −1 t/746db2_400.t
  56. +1 −1 t/746mssql.t
  57. +3 −3 t/746sybase.t
  58. +1 −1 t/748informix.t
  59. +1 −1 t/749sqlanywhere.t
  60. +2 −2 t/75limit.t
  61. +3 −3 t/76joins.t
  62. +1 −1 t/78self_referencial.t
  63. +1 −1 t/79aliasing.t
  64. +1 −1 t/83cache.t
  65. +4 −4 t/86might_have.t
  66. +24 −24 t/86sqlt.t
  67. +10 −10 t/87ordered.t
  68. +1 −1 t/90ensure_class_loaded.t
  69. +1 −1 t/91merge_joinpref_attr.t
  70. +1 −1 t/93single_accessor_object.t
  71. +1 −1 t/94pk_mutation.t
  72. +2 −2 t/94versioning.t
  73. +7 −7 t/97result_class.t
  74. +1 −1 t/99dbic_sqlt_parser.t
  75. +1 −1 t/admin/03data.t
  76. +4 −4 t/cdbi/02-Film.t
  77. +9 −9 t/cdbi/04-lazy.t
  78. +1 −1 t/cdbi/06-hasa.t
  79. +1 −1 t/cdbi/11-triggers.t
  80. +1 −1 t/cdbi/14-might_have.t
  81. +10 −10 t/cdbi/19-set_sql.t
  82. +1 −1 t/cdbi/23-cascade.t
  83. +2 −2 t/cdbi/24-meta_info.t
  84. +1 −1 t/cdbi/26-mutator.t
  85. +1 −1 t/cdbi/30-pager.t
  86. +1 −1 t/cdbi/abstract/search_where.t
  87. +6 −6 t/cdbi/columns_as_hashes.t
  88. +1 −1 t/cdbi/construct.t
  89. +1 −1 t/cdbi/copy.t
  90. +2 −2 t/cdbi/object_cache.t
  91. +2 −2 t/cdbi/sweet/08pager.t
  92. +2 −2 t/cdbi/testlib/Actor.pm
  93. +1 −1 t/cdbi/testlib/ActorAlias.pm
  94. +1 −1 t/cdbi/testlib/CDBase.pm
  95. +1 −1 t/cdbi/testlib/DBIC/Test/SQLite.pm
  96. +1 −1 t/cdbi/testlib/Director.pm
  97. +2 −2 t/cdbi/testlib/Film.pm
  98. +1 −1 t/cdbi/testlib/Lazy.pm
  99. +1 −1 t/cdbi/testlib/Log.pm
  100. +1 −1 t/cdbi/testlib/MyFilm.pm
  101. +1 −1 t/cdbi/testlib/MyFoo.pm
  102. +1 −1 t/cdbi/testlib/MyStar.pm
  103. +1 −1 t/cdbi/testlib/MyStarLink.pm
  104. +1 −1 t/cdbi/testlib/MyStarLinkMCPK.pm
  105. +1 −1 t/cdbi/testlib/Order.pm
  106. +2 −2 t/count/distinct.t
  107. +1 −1 t/discard_changes_in_DESTROY.t
  108. +1 −1 t/inflate/core.t
  109. +3 −3 t/inflate/datetime_firebird.t
  110. +2 −2 t/inflate/datetime_informix.t
  111. +2 −2 t/inflate/datetime_sqlanywhere.t
  112. +1 −1 t/inflate/hri.t
  113. +2 −2 t/inflate/serialize.t
  114. +3 −3 t/lib/DBIC/SqlMakerTest.pm
  115. +14 −14 t/lib/DBICTest.pm
  116. +1 −1 t/lib/DBICTest/ErrorComponent.pm
  117. +1 −1 t/lib/DBICTest/FakeComponent.pm
  118. +1 −1 t/lib/DBICTest/ForeignComponent.pm
  119. +1 −1 t/lib/DBICTest/OptionalComponent.pm
  120. +1 −1 t/lib/DBICTest/ResultSetManager.pm
  121. +1 −1 t/lib/DBICTest/ResultSetManager/Foo.pm
  122. +1 −1 t/lib/DBICTest/Schema/Artist.pm
  123. +1 −1 t/lib/DBICTest/Schema/ArtistGUID.pm
  124. +1 −1 t/lib/DBICTest/Schema/ArtistUndirectedMap.pm
  125. +1 −1 t/lib/DBICTest/Schema/BindType.pm
  126. +1 −1 t/lib/DBICTest/Schema/BooksInLibrary.pm
  127. +8 −8 t/lib/DBICTest/Schema/CD.pm
  128. +1 −1 t/lib/DBICTest/Schema/CD_to_Producer.pm
  129. +2 −2 t/lib/DBICTest/Schema/Collection.pm
  130. +1 −1 t/lib/DBICTest/Schema/CollectionObject.pm
  131. +1 −1 t/lib/DBICTest/Schema/ComputedColumn.pm
  132. +2 −2 t/lib/DBICTest/Schema/CustomSql.pm
  133. +1 −1 t/lib/DBICTest/Schema/Employee.pm
  134. +1 −1 t/lib/DBICTest/Schema/FourKeys.pm
  135. +1 −1 t/lib/DBICTest/Schema/FourKeys_to_TwoKeys.pm
  136. +1 −1 t/lib/DBICTest/Schema/Image.pm
  137. +1 −1 t/lib/DBICTest/Schema/LinerNotes.pm
  138. +1 −1 t/lib/DBICTest/Schema/Lyrics.pm
  139. +1 −1 t/lib/DBICTest/Schema/Money.pm
  140. +1 −1 t/lib/DBICTest/Schema/NoPrimaryKey.pm
  141. +1 −1 t/lib/DBICTest/Schema/OneKey.pm
  142. +1 −1 t/lib/DBICTest/Schema/Owners.pm
  143. +1 −1 t/lib/DBICTest/Schema/Producer.pm
  144. +1 −1 t/lib/DBICTest/Schema/PunctuatedColumnName.pm
  145. +1 −1 t/lib/DBICTest/Schema/SelfRef.pm
  146. +1 −1 t/lib/DBICTest/Schema/SelfRefAlias.pm
  147. +1 −1 t/lib/DBICTest/Schema/SequenceTest.pm
  148. +1 −1 t/lib/DBICTest/Schema/Serialized.pm
  149. +1 −1 t/lib/DBICTest/Schema/Tag.pm
  150. +1 −1 t/lib/DBICTest/Schema/TimestampPrimaryKey.pm
  151. +1 −1 t/lib/DBICTest/Schema/TreeLike.pm
  152. +1 −1 t/lib/DBICTest/Schema/TwoKeyTreeLike.pm
  153. +1 −1 t/lib/DBICTest/Schema/TypedObject.pm
  154. +1 −1 t/lib/DBICTest/Schema/Year1999CDs.pm
  155. +1 −1 t/lib/DBICTest/SyntaxErrorComponent1.pm
  156. +1 −1 t/lib/DBICTest/SyntaxErrorComponent2.pm
  157. +1 −1 t/lib/DBICTest/Taint/Classes/Auto.pm
  158. +1 −1 t/lib/DBICTest/Taint/Classes/Manual.pm
  159. +1 −1 t/lib/DBICTest/Taint/Namespaces/Result/Test.pm
  160. +2 −2 t/lib/sqlite.sql
  161. +1 −1 t/multi_create/existing_in_chain.t
  162. +1 −1 t/multi_create/in_memory.t
  163. +25 −25 t/multi_create/standard.t
  164. +4 −4 t/multi_create/torture.t
  165. +1 −1 t/ordered/cascade_delete.t
  166. +1 −1 t/prefetch/attrs_untouched.t
  167. +1 −1 t/prefetch/diamond.t
  168. +1 −1 t/prefetch/incomplete.t
  169. +1 −1 t/prefetch/multiple_hasmany.t
  170. +2 −2 t/prefetch/standard.t
  171. +6 −6 t/relationship/core.t
  172. +1 −1 t/relationship/update_or_create_multi.t
  173. +1 −1 t/resultset/as_subselect_rs.t
  174. +3 −3 t/resultset/bind_attr.t
  175. +3 −3 t/resultset/is_ordered.t
  176. +2 −2 t/resultset/update_delete.t
  177. +1 −1 t/sqlmaker/limit_dialects/fetch_first.t
  178. +1 −1 t/sqlmaker/limit_dialects/first_skip.t
  179. +1 −1 t/sqlmaker/limit_dialects/skip_first.t
  180. +2 −2 t/sqlmaker/oracle.t
  181. +3 −3 t/sqlmaker/order_by_bindtransport.t
  182. +1 −1 t/storage/txn.t
  183. +1 −1 t/update/type_aware.t
  184. +6 −15 xt/eol.t
  185. +2 −6 xt/notabs.t
  186. +0 −5 xt/pod.t
  187. +0 −5 xt/podcoverage.t
View
@@ -3,6 +3,9 @@ Revision history for DBIx::Class
* Fixes
- Fix SkipFirst and FirstSkip limit dialects (Informix and Firebird)
+ * Misc
+ - Codebase is now trailing-whitespace-free
+
0.08196 2011-11-29 05:35 (UTC)
* Fixes
- Fix tests for DBD::SQLite >= 1.34.
@@ -66,7 +66,7 @@ sub pod_option_text {
$spec = Getopt::Long::Descriptive->_strip_assignment($spec);
$string .= "=item " . join " or ", map { length > 1 ? "B<--$_>" : "B<-$_>" }
- split /\|/, $spec;
+ split /\|/, $spec;
$string .= "\n\n$desc\n\n=cut\n\n";
}
@@ -62,7 +62,7 @@ DBIx::Class::CDBICompat - Class::DBI Compatibility layer.
=head1 DESCRIPTION
DBIx::Class features a fully featured compatibility layer with L<Class::DBI>
-and some common plugins to ease transition for existing CDBI users.
+and some common plugins to ease transition for existing CDBI users.
This is not a wrapper or subclass of DBIx::Class but rather a series of plugins. The result being that even though you're using the Class::DBI emulation layer you are still getting DBIx::Class objects. You can use all DBIx::Class features and methods via CDBICompat. This allows you to take advantage of DBIx::Class features without having to rewrite your CDBI code.
@@ -91,7 +91,7 @@ This plugin will work, but it is more efficiently done using DBIC's native searc
=head2 Choosing Features
In fact, this class is just a recipe containing all the features emulated.
-If you like, you can choose which features to emulate by building your
+If you like, you can choose which features to emulate by building your
own class and loading it like this:
package My::DB;
@@ -35,17 +35,17 @@ sub mk_group_accessors {
sub accessor_name_for {
my ($class, $column) = @_;
- if ($class->can('accessor_name')) {
- return $class->accessor_name($column)
+ if ($class->can('accessor_name')) {
+ return $class->accessor_name($column)
}
return $column;
}
sub mutator_name_for {
my ($class, $column) = @_;
- if ($class->can('mutator_name')) {
- return $class->mutator_name($column)
+ if ($class->can('mutator_name')) {
+ return $class->mutator_name($column)
}
return $column;
@@ -12,7 +12,7 @@ sub resultset_instance {
}
-# Emulate that CDBI throws out all changed columns and reloads them on
+# Emulate that CDBI throws out all changed columns and reloads them on
# request in case the database modifies the new value (say, via a trigger)
sub update {
my $self = shift;
View
@@ -184,8 +184,8 @@ sub result_source_instance {
if ($result_class ne $class) { # new class
# Give this new class its own source and register it.
- $source = $source->new({
- %$source,
+ $source = $source->new({
+ %$source,
source_name => $class,
result_class => $class
} );
@@ -29,7 +29,7 @@ sub register_column {
return unless defined($info->{is_file_column});
$self->inflate_column($column => {
- inflate => sub {
+ inflate => sub {
my ($value, $obj) = @_;
$obj->_inflate_file_column($column, $value);
},
@@ -155,7 +155,7 @@ In your L<DBIx::Class> table class:
data_type => "varchar",
is_file_column => 1,
file_column_path =>'/tmp/uploaded_files',
- # or for a Catalyst application
+ # or for a Catalyst application
# file_column_path => MyApp->path_to('root','static','files'),
default_value => undef,
is_nullable => 1,
@@ -169,11 +169,11 @@ In your L<Catalyst::Controller> class:
FileColumn requires a hash that contains L<IO::File> as handle and the file's
name as name.
- my $entry = $c->model('MyAppDB::Articles')->create({
+ my $entry = $c->model('MyAppDB::Articles')->create({
subject => 'blah',
- filename => {
- handle => $c->req->upload('myupload')->fh,
- filename => $c->req->upload('myupload')->basename
+ filename => {
+ handle => $c->req->upload('myupload')->fh,
+ filename => $c->req->upload('myupload')->basename
},
body => '....'
});
@@ -183,7 +183,7 @@ name as name.
And Place the following in your TT template
Article Subject: [% entry.subject %]
- Uploaded File:
+ Uploaded File:
<a href="/static/files/[% entry.id %]/[% entry.filename.filename %]">File</a>
Body: [% entry.body %]
@@ -1,10 +1,10 @@
-=head1 NAME
+=head1 NAME
DBIx::Class::Manual - Index of the Manual
=head1 DESCRIPTION
-This is the L<DBIx::Class> users manual. DBIx::Class is a SQL->OOP mapper.
+This is the L<DBIx::Class> users manual. DBIx::Class is a SQL->OOP mapper.
This means that it can represent your SQL tables as perl classes, and give
you convenient accessors and methods for retrieving and updating information
from your SQL database.
@@ -21,7 +21,7 @@ Explanations of terms used in this documentation.
=head2 L<DBIx::Class::Manual::Intro>
-Beginner guide to using DBIx::Class.
+Beginner guide to using DBIx::Class.
=head2 L<DBIx::Class::Manual::Example>
@@ -52,7 +52,7 @@ documentation. It should behave the same way.
=head2 L<DBIx::Class::Manual::Component>
-Existing components, and documentation and example on how to
+Existing components, and documentation and example on how to
develop new ones.
=cut
@@ -134,8 +134,8 @@ as you like. See L<DBIx::Class::Relationship::Base>.
=item .. define a relationship bridge across an intermediate table? (many-to-many)
-The term 'relationship' is used loosely with many_to_many as it is not considered a
-relationship in the fullest sense. For more info, read the documentation on L<DBIx::Class::Relationship/many_to_many>.
+The term 'relationship' is used loosely with many_to_many as it is not considered a
+relationship in the fullest sense. For more info, read the documentation on L<DBIx::Class::Relationship/many_to_many>.
=item .. stop DBIx::Class from attempting to cascade deletes on my has_many and might_have relationships?
@@ -437,8 +437,8 @@ data out.
=head2 Custom methods in Result classes
-You can add custom methods that do arbitrary things, even to unrelated tables.
-For example, to provide a C<< $book->foo() >> method which searches the
+You can add custom methods that do arbitrary things, even to unrelated tables.
+For example, to provide a C<< $book->foo() >> method which searches the
cd table, you'd could add this to Book.pm:
sub foo {
@@ -455,7 +455,7 @@ methods to find or create data in related tables for you. But if you want to
write your own methods, you can.
For example, to provide a C<< $book->foo() >> method to manually implement
-what create_related() from L<DBIx::Class::Relationship::Base> does, you could
+what create_related() from L<DBIx::Class::Relationship::Base> does, you could
add this to Book.pm:
sub foo {
@@ -567,12 +567,12 @@ The code example works for both modules:
package Your::Schema::Group;
use Class::Method::Modifiers;
-
+
# ... declare columns ...
-
+
__PACKAGE__->has_many('group_servers', 'Your::Schema::GroupServer', 'group_id');
__PACKAGE__->many_to_many('servers', 'group_servers', 'server');
-
+
# if the server group is a "super group", then return all servers
# otherwise return only servers that belongs to the given group
around 'servers' => sub {
@@ -592,12 +592,12 @@ L<Method::Signatures::Simple> way:
package Your::Schema::Group;
use Method::Signatures::Simple;
-
+
# ... declare columns ...
-
+
__PACKAGE__->has_many('group_servers', 'Your::Schema::GroupServer', 'group_id');
__PACKAGE__->many_to_many('servers', 'group_servers', 'server');
-
+
# The method keyword automatically injects the annoying my $self = shift; for you.
method servers {
return $self->result_source->schema->resultset('Server')->search({ ... });
@@ -607,17 +607,17 @@ The dirty way:
package Your::Schema::Group;
use Sub::Name;
-
+
# ... declare columns ...
-
+
__PACKAGE__->has_many('group_servers', 'Your::Schema::GroupServer', 'group_id');
__PACKAGE__->many_to_many('servers', 'group_servers', 'server');
-
+
*servers = subname servers => sub {
my $self = shift;
return $self->result_source->schema->resultset('Server')->search({ ... });
};
-
+
=back
=head2 Notes for CDBI users
@@ -55,7 +55,7 @@ condition between the tables.
=head2 Relationship bridge
A relationship bridge, such as C<many_to_many> defines an accessor to
-retrieve row contents across multiple relationships.
+retrieve row contents across multiple relationships.
The difference between a bridge and a relationship is, that the bridge
cannot be used to C<join> tables in a C<search>, instead its component
@@ -116,7 +116,7 @@ automatic row ordering:
__PACKAGE__->position_column('rank');
Ordered will refer to a field called 'position' unless otherwise directed. Here you are defining
-the ordering field to be named 'rank'. (NOTE: Insert errors may occur if you use the Ordered
+the ordering field to be named 'rank'. (NOTE: Insert errors may occur if you use the Ordered
component, but have not defined a position column or have a 'position' field in your row.)
Set the table for your class:
@@ -1,4 +1,4 @@
-=head1 NAME
+=head1 NAME
DBIx::Class::Manual::Joining - Manual on joining tables with DBIx::Class
@@ -175,14 +175,14 @@ has a very large field you don't need for the current data
output. This is better solved by storing that field in a separate
table which you only join to when needed.
-To fetch an incomplete related object, supply the dotted notation to the '+as' attribute:
+To fetch an incomplete related object, supply the dotted notation to the '+as' attribute:
$schema->resultset('CD')->search(
{ 'Title' => 'Funky CD',
},
{ join => 'tracks',
'+select' => ['tracks.Name'],
- '+as' => ['tracks.Name'],
+ '+as' => ['tracks.Name'],
order_by => ['tracks.id'],
}
);
@@ -232,13 +232,13 @@ Which is:
To perform joins using relations of the tables you are joining to, use
a hashref to indicate the join depth. This can theoretically go as
-deep as you like (warning: contrived examples!):
+deep as you like (warning: contrived examples!):
join => { room => { table => 'leg' } }
To join two relations at the same level, use an arrayref instead:
- join => { room => [ 'chair', 'table' ] }
+ join => { room => [ 'chair', 'table' ] }
Or combine the two:
@@ -105,7 +105,7 @@ caller should pass C<undef> in place of the missing argument.
=item *
-| - Alternate argument content types.
+| - Alternate argument content types.
At least one of these must be supplied unless the argument is also
marked optional.
@@ -51,7 +51,7 @@ L<DBI> version 1.50 and L<DBD::Pg> 1.43 are known to work.
There's likely a syntax error in the table class referred to elsewhere
in this error message. In particular make sure that the package
-declaration is correct. For example, for a schema C< MySchema >
+declaration is correct. For example, for a schema C< MySchema >
you need to specify a fully qualified namespace: C< package MySchema::MyTable; >.
=head2 syntax error at or near "<something>" ...
@@ -149,11 +149,11 @@ L<http://rhn.redhat.com/errata/RHBA-2008-0876.html>
=head2 Excessive Memory Allocation with TEXT/BLOB/etc. Columns and Large LongReadLen
-It has been observed, using L<DBD::ODBC>, that creating a L<DBIx::Class::Row>
-object which includes a column of data type TEXT/BLOB/etc. will allocate
-LongReadLen bytes. This allocation does not leak, but if LongReadLen
-is large in size, and many such row objects are created, e.g. as the
-output of a ResultSet query, the memory footprint of the Perl interpreter
+It has been observed, using L<DBD::ODBC>, that creating a L<DBIx::Class::Row>
+object which includes a column of data type TEXT/BLOB/etc. will allocate
+LongReadLen bytes. This allocation does not leak, but if LongReadLen
+is large in size, and many such row objects are created, e.g. as the
+output of a ResultSet query, the memory footprint of the Perl interpreter
can grow very large.
The solution is to use the smallest practical value for LongReadLen.
@@ -183,7 +183,7 @@ my $reqs = {
test_eol => {
req => {
- 'Test::EOL' => '0.6',
+ 'Test::EOL' => '1.0',
},
},
@@ -370,7 +370,7 @@ my $reqs = {
title => 'Informix support',
desc => 'Modules required to connect to Informix',
},
- },
+ },
rdbms_sqlanywhere => {
req => {
@@ -380,7 +380,7 @@ my $reqs = {
title => 'SQLAnywhere support',
desc => 'Modules required to connect to SQLAnywhere',
},
- },
+ },
rdbms_sqlanywhere_odbc => {
req => {
@@ -390,7 +390,7 @@ my $reqs = {
title => 'SQLAnywhere support via DBD::ODBC',
desc => 'Modules required to connect to SQLAnywhere via DBD::ODBC',
},
- },
+ },
rdbms_firebird => {
req => {
@@ -400,7 +400,7 @@ my $reqs = {
title => 'Firebird support',
desc => 'Modules required to connect to Firebird',
},
- },
+ },
rdbms_firebird_interbase => {
req => {
@@ -410,7 +410,7 @@ my $reqs = {
title => 'Firebird support via DBD::InterBase',
desc => 'Modules required to connect to Firebird via DBD::InterBase',
},
- },
+ },
rdbms_firebird_odbc => {
req => {
@@ -420,7 +420,7 @@ my $reqs = {
title => 'Firebird support via DBD::ODBC',
desc => 'Modules required to connect to Firebird via DBD::ODBC',
},
- },
+ },
# the order does matter because the rdbms support group might require
# a different version that the test group
Oops, something went wrong.

0 comments on commit 8273e84

Please sign in to comment.