added DBIx::Custom::Guides
|
1 |
=head1 NAME |
2 | ||
3 |
DBIx::Custom::Guides - DBIx::Custom Guides |
|
4 | ||
5 |
=head1 GUIDES |
|
6 | ||
7 |
=head2 1. Connect to the database |
|
8 | ||
9 |
use DBIx::Custom; |
|
remove DBIx::Custom::Model
|
10 |
my $dbi = DBIx::Custom->connect(data_source => "dbi:mysql:database=$database", |
added DBIx::Custom::Guides
|
11 |
user => 'ken', password => '!LFKD%$&'); |
12 | ||
remove DBIx::Custom::Model
|
13 |
use C<connect()> to connect to the database. |
14 |
You can sepecfiy C<data_soruce>, C<user>, and C<password>. |
|
deprecated DBIx::Custom::MyS...
|
15 | |
remove DBIx::Custom::Model
|
16 |
The following ones are data source exmaple in variouse dabase system. |
deprecated DBIx::Custom::MyS...
|
17 | |
18 |
SQLite |
|
19 | ||
20 |
"dbi:SQLite:dbname=$database" |
|
21 |
"dbi:SQLite:dbname=:memory:" |
|
22 | ||
remove DBIx::Custom::Model
|
23 |
MySQL |
24 | ||
25 |
"dbi:mysql:database=$database" |
|
26 |
"dbi:mysql:database=$database;host=$hostname;port=$port" |
|
27 | ||
deprecated DBIx::Custom::MyS...
|
28 |
PostgreSQL |
29 | ||
30 |
"dbi:Pg:dbname=$dbname" |
|
31 | ||
32 |
Oracle |
|
33 | ||
34 |
"dbi:Oracle:$dbname" |
|
35 |
"dbi:Oracle:host=$host;sid=$sid" |
|
36 | ||
37 |
ODBC(Microsoft Access) |
|
38 | ||
39 |
"dbi:ODBC:driver=Microsoft Access Driver (*.mdb);dbq=hoge.mdb" |
|
40 | ||
41 |
ODBC(SQL Server) |
|
42 | ||
43 |
"dbi:ODBC:driver={SQL Server};Server=(local);database=test;Trusted_Connection=yes;AutoTranslate=No;" |
|
added DBIx::Custom::Guides
|
44 | |
45 |
=head2 2. Suger methods |
|
46 | ||
47 |
L<DBIx::Custom> has suger methods, such as C<insert()>, C<update()>, |
|
48 |
C<delete()> or C<select()>. If you want to do small works, |
|
49 |
You don't have to create SQL statements. |
|
50 | ||
51 |
=head3 insert() |
|
52 | ||
53 |
Execute insert statement. |
|
54 | ||
remove DBIx::Custom::Model
|
55 |
$dbi->insert(table => 'book', |
added DBIx::Custom::Guides
|
56 |
param => {title => 'Perl', author => 'Ken'}); |
57 | ||
58 |
The following SQL is executed. |
|
59 | ||
60 |
insert into (title, author) values (?, ?); |
|
61 | ||
62 |
The values of C<title> and C<author> is embedded into the placeholders. |
|
63 | ||
64 |
C<append> and C<filter> argument can be specified. |
|
65 |
See also "METHODS" section. |
|
66 | ||
67 |
=head3 update() |
|
68 | ||
69 |
Execute update statement. |
|
70 | ||
remove DBIx::Custom::Model
|
71 |
$dbi->update(table => 'book', |
added DBIx::Custom::Guides
|
72 |
param => {title => 'Perl', author => 'Ken'}, |
73 |
where => {id => 5}); |
|
74 | ||
75 |
The following SQL is executed. |
|
76 | ||
remove DBIx::Custom::Model
|
77 |
update book set title = ?, author = ?; |
added DBIx::Custom::Guides
|
78 | |
79 |
The values of C<title> and C<author> is embedded into the placeholders. |
|
80 | ||
81 |
C<append> and C<filter> argument can be specified. |
|
82 |
See also "METHOD" section. |
|
83 | ||
84 |
If you want to update all rows, use C<update_all()> method. |
|
85 | ||
86 |
=head3 delete() |
|
87 | ||
88 |
Execute delete statement. |
|
89 | ||
remove DBIx::Custom::Model
|
90 |
$dbi->delete(table => 'book', |
added DBIx::Custom::Guides
|
91 |
where => {author => 'Ken'}); |
92 | ||
93 |
The following SQL is executed. |
|
94 | ||
remove DBIx::Custom::Model
|
95 |
delete from book where id = ?; |
added DBIx::Custom::Guides
|
96 | |
97 |
The value of C<id> is embedded into the placehodler. |
|
98 | ||
99 |
C<append> and C<filter> argument can be specified. |
|
100 |
see also "METHODS" section. |
|
101 | ||
102 |
If you want to delete all rows, use C<delete_all()> method. |
|
103 | ||
104 |
=head3 select() |
|
105 | ||
106 |
Execute select statement, only C<table> argument specified : |
|
107 | ||
remove DBIx::Custom::Model
|
108 |
my $result = $dbi->select(table => 'book'); |
added DBIx::Custom::Guides
|
109 | |
110 |
The following SQL is executed. |
|
111 | ||
remove DBIx::Custom::Model
|
112 |
select * from book; |
added DBIx::Custom::Guides
|
113 | |
114 |
the result of C<select()> method is L<DBIx::Custom::Result> object. |
|
115 |
You can fetch a row by C<fetch()> method. |
|
116 | ||
117 |
while (my $row = $result->fetch) { |
|
118 |
my $title = $row->[0]; |
|
119 |
my $author = $row->[1]; |
|
120 |
} |
|
121 | ||
122 |
L<DBIx::Custom::Result> has various methods to fetch row. |
|
123 |
See "3. Fetch row". |
|
124 | ||
125 |
C<column> and C<where> arguments specified. |
|
126 | ||
127 |
my $result = $dbi->select( |
|
remove DBIx::Custom::Model
|
128 |
table => 'book', |
added DBIx::Custom::Guides
|
129 |
column => [qw/author title/], |
130 |
where => {author => 'Ken'} |
|
131 |
); |
|
132 | ||
133 |
The following SQL is executed. |
|
134 | ||
remove DBIx::Custom::Model
|
135 |
select author, title from book where author = ?; |
added DBIx::Custom::Guides
|
136 | |
137 |
the value of C<author> is embdded into the placeholder. |
|
138 | ||
139 |
If you want to join tables, specify C<relation> argument. |
|
140 | ||
141 |
my $result = $dbi->select( |
|
remove DBIx::Custom::Model
|
142 |
table => ['book', 'rental'], |
143 |
column => ['book.name as book_name'] |
|
144 |
relation => {'book.id' => 'rental.book_id'} |
|
added DBIx::Custom::Guides
|
145 |
); |
146 | ||
147 |
The following SQL is executed. |
|
148 | ||
remove DBIx::Custom::Model
|
149 |
select book.name as book_name from book, rental |
150 |
where book.id = rental.book_id; |
|
added DBIx::Custom::Guides
|
151 | |
152 |
If you want to add some string to the end of SQL statement, |
|
153 |
use C<append> argument. |
|
154 | ||
155 |
my $result = $dbi->select( |
|
remove DBIx::Custom::Model
|
156 |
table => 'book', |
added DBIx::Custom::Guides
|
157 |
where => {author => 'Ken'}, |
158 |
append => 'order by price limit 5', |
|
159 |
); |
|
160 | ||
161 |
The following SQL is executed. |
|
162 | ||
remove DBIx::Custom::Model
|
163 |
select * book where author = ? order by price limit 5; |
added DBIx::Custom::Guides
|
164 | |
165 |
C<filter> argument can be specified. |
|
166 |
see also "METHODS" section. |
|
167 | ||
168 |
=head2 3. Fetch row |
|
169 | ||
170 |
C<select()> method return L<DBIx::Custom::Result> object. |
|
171 |
You can fetch row by various methods. |
|
172 |
Note that in this section, array means array reference, |
|
173 |
and hash meanse hash reference. |
|
174 | ||
175 |
Fetch row into array. |
|
176 |
|
|
177 |
while (my $row = $result->fetch) { |
|
178 |
my $author = $row->[0]; |
|
179 |
my $title = $row->[1]; |
|
180 |
|
|
181 |
} |
|
182 | ||
183 |
Fetch only a first row into array. |
|
184 | ||
185 |
my $row = $result->fetch_first; |
|
186 | ||
187 |
Fetch multiple rows into array of array. |
|
188 | ||
189 |
while (my $rows = $result->fetch_multi(5)) { |
|
190 |
my $first_author = $rows->[0][0]; |
|
191 |
my $first_title = $rows->[0][1]; |
|
192 |
my $second_author = $rows->[1][0]; |
|
193 |
my $second_value = $rows->[1][1]; |
|
194 |
|
|
195 |
} |
|
196 |
|
|
197 |
Fetch all rows into array of array. |
|
198 | ||
199 |
my $rows = $result->fetch_all; |
|
200 | ||
201 |
Fetch row into hash. |
|
202 | ||
203 |
# Fetch a row into hash |
|
204 |
while (my $row = $result->fetch_hash) { |
|
205 |
my $title = $row->{title}; |
|
206 |
my $author = $row->{author}; |
|
207 |
|
|
208 |
} |
|
209 | ||
210 |
Fetch only a first row into hash |
|
211 | ||
212 |
my $row = $result->fetch_hash_first; |
|
213 |
|
|
214 |
Fetch multiple rows into array of hash |
|
215 | ||
216 |
while (my $rows = $result->fetch_hash_multi(5)) { |
|
217 |
my $first_title = $rows->[0]{title}; |
|
218 |
my $first_author = $rows->[0]{author}; |
|
219 |
my $second_title = $rows->[1]{title}; |
|
220 |
my $second_author = $rows->[1]{author}; |
|
221 |
|
|
222 |
} |
|
223 |
|
|
224 |
Fetch all rows into array of hash |
|
225 | ||
226 |
my $rows = $result->fetch_hash_all; |
|
227 | ||
228 |
If you want to access statement handle of L<DBI>, use C<sth> attribute. |
|
229 | ||
230 |
my $sth = $result->sth; |
|
231 | ||
232 |
=head2 4. Hash parameter binding |
|
233 | ||
234 |
L<DBIx::Custom> provides hash parameter binding. |
|
235 | ||
236 |
At frist, I show normal parameter binding. |
|
237 | ||
238 |
use DBI; |
|
239 |
my $dbh = DBI->connect(...); |
|
240 |
my $sth = $dbh->prepare( |
|
remove DBIx::Custom::Model
|
241 |
"select * from book where author = ? and title like ?;" |
added DBIx::Custom::Guides
|
242 |
); |
243 |
$sth->execute('Ken', '%Perl%'); |
|
244 | ||
245 |
This is very good way because database system can enable SQL caching, |
|
246 |
and parameter is quoted automatically. this is secure. |
|
247 | ||
248 |
L<DBIx::Custom> hash parameter binding system improve |
|
249 |
normal parameter binding to use hash parameter. |
|
250 | ||
251 |
my $result = $dbi->execute( |
|
remove DBIx::Custom::Model
|
252 |
"select * from book where {= author} and {like title};" |
added DBIx::Custom::Guides
|
253 |
param => {author => 'Ken', title => '%Perl%'} |
254 |
); |
|
255 | ||
256 |
This is same as the normal way, execpt that the parameter is hash. |
|
257 |
{= author} and {like title} is called C<tag>. |
|
258 |
tag is expand to placeholder string internally. |
|
259 | ||
remove DBIx::Custom::Model
|
260 |
select * from book where {= author} and {like title} |
261 |
-> select * from book where author = ? and title like ?; |
|
added DBIx::Custom::Guides
|
262 | |
263 |
The following tags is available. |
|
264 | ||
265 |
[TAG] [REPLACED] |
|
266 |
{? NAME} -> ? |
|
267 |
{= NAME} -> NAME = ? |
|
268 |
{<> NAME} -> NAME <> ? |
|
269 |
|
|
270 |
{< NAME} -> NAME < ? |
|
271 |
{> NAME} -> NAME > ? |
|
272 |
{>= NAME} -> NAME >= ? |
|
273 |
{<= NAME} -> NAME <= ? |
|
274 |
|
|
275 |
{like NAME} -> NAME like ? |
|
276 |
{in NAME COUNT} -> NAME in [?, ?, ..] |
|
277 |
|
|
278 |
{insert_param NAME1 NAME2} -> (NAME1, NAME2) values (?, ?) |
|
279 |
{update_param NAME1 NAME2} -> set NAME1 = ?, NAME2 = ? |
|
280 | ||
281 |
See also L<DBIx::Custom::QueryBuilder>. |
|
282 | ||
283 |
C<{> and C<}> is reserved. If you use these charactors, |
|
284 |
you must escape them using '\'. Note that '\' is |
|
285 |
already perl escaped charactor, so you must write '\\'. |
|
286 | ||
remove DBIx::Custom::Model
|
287 |
'select * from book \\{ something statement \\}' |
added DBIx::Custom::Guides
|
288 | |
289 |
=head2 5. Filtering |
|
290 | ||
291 |
Usually, Perl string is kept as internal string. |
|
292 |
If you want to save the string to database, You must encode the string. |
|
293 |
Filtering system help you to convert a data to another data |
|
294 |
when you save to the data and get the data form database. |
|
295 | ||
296 |
If you want to register filter, use C<register_filter()> method. |
|
297 | ||
298 |
$dbi->register_filter( |
|
299 |
to_upper_case => sub { |
|
300 |
my $value = shift; |
|
301 |
return uc $value; |
|
302 |
} |
|
303 |
); |
|
304 | ||
305 |
C<encode_utf8> and C<decode_utf8> filter is registerd by default. |
|
306 | ||
307 |
You can specify these filters to C<filter> argument of C<execute()> method. |
|
308 | ||
309 |
my $result = $dbi->execute( |
|
remove DBIx::Custom::Model
|
310 |
"select * from book where {= author} and {like title};" |
added DBIx::Custom::Guides
|
311 |
param => {author => 'Ken', title => '%Perl%'}, |
312 |
filter => {author => 'to_upper_case, title => 'encode_utf8'} |
|
313 |
); |
|
314 | ||
315 |
C<filter> argument can be specified to suger methods, such as |
|
316 |
C<insert()>, C<update()>, C<update_all()>, |
|
317 |
C<delete()>, C<delete_all()>, C<select()>. |
|
318 | ||
319 |
# insert(), having filter argument |
|
remove DBIx::Custom::Model
|
320 |
$dbi->insert(table => 'book', |
added DBIx::Custom::Guides
|
321 |
param => {title => 'Perl', author => 'Ken'}, |
322 |
filter => {title => 'encode_utf8'}); |
|
323 |
|
|
324 |
# select(), having filter argument |
|
325 |
my $result = $dbi->select( |
|
remove DBIx::Custom::Model
|
326 |
table => 'book', |
added DBIx::Custom::Guides
|
327 |
column => [qw/author title/], |
328 |
where => {author => 'Ken'}, |
|
329 |
append => 'order by id limit 1', |
|
330 |
filter => {title => 'encode_utf8'} |
|
331 |
); |
|
332 | ||
333 |
Filter works each parmeter, but you prepare default filter for all parameters. |
|
334 | ||
335 |
$dbi->default_bind_filter('encode_utf8'); |
|
336 | ||
337 |
C<filter()> argument overwrites this default filter. |
|
338 |
|
|
339 |
$dbi->default_bind_filter('encode_utf8'); |
|
340 |
$dbi->insert( |
|
remove DBIx::Custom::Model
|
341 |
table => 'book', |
added DBIx::Custom::Guides
|
342 |
param => {title => 'Perl', author => 'Ken', price => 1000}, |
343 |
filter => {author => 'to_upper_case', price => undef} |
|
344 |
); |
|
345 | ||
346 |
This is same as the following example. |
|
347 | ||
348 |
$dbi->insert( |
|
remove DBIx::Custom::Model
|
349 |
table => 'book', |
added DBIx::Custom::Guides
|
350 |
param => {title => 'Perl', author => 'Ken', price => 1000}, |
351 |
filter => {title => 'encode_uft8' author => 'to_upper_case'} |
|
352 |
); |
|
353 | ||
354 |
You can also specify filter when the row is fetched. This is reverse of bind filter. |
|
355 | ||
remove DBIx::Custom::Model
|
356 |
my $result = $dbi->select(table => 'book'); |
added DBIx::Custom::Guides
|
357 |
$result->filter({title => 'decode_utf8', author => 'to_upper_case'}); |
358 | ||
359 |
Filter works each column value, but you prepare a default filter |
|
360 |
for all clumn value. |
|
361 | ||
362 |
$dbi->default_fetch_filter('decode_utf8'); |
|
363 | ||
364 |
C<filter()> method of L<DBIx::Custom::Result> |
|
365 |
overwrites this default filter. |
|
366 | ||
367 |
$dbi->default_fetch_filter('decode_utf8'); |
|
368 |
my $result = $dbi->select( |
|
remove DBIx::Custom::Model
|
369 |
table => 'book', |
added DBIx::Custom::Guides
|
370 |
columns => ['title', 'author', 'price'] |
371 |
); |
|
372 |
$result->filter({author => 'to_upper_case', price => undef}); |
|
373 | ||
374 |
This is same as the following one. |
|
375 | ||
376 |
my $result = $dbi->select( |
|
remove DBIx::Custom::Model
|
377 |
table => 'book', |
added DBIx::Custom::Guides
|
378 |
columns => ['title', 'author', 'price'] |
379 |
); |
|
380 |
$result->filter({title => 'decode_utf8', author => 'to_upper_case'}); |
|
381 | ||
382 |
Note that in fetch filter, column names must be lower case |
|
383 |
even if the column name conatains upper case charactors. |
|
384 |
This is requirment not to depend database systems. |
|
385 | ||
check arguments of connect m...
|
386 |
B<Filter examples> |
387 | ||
388 |
MySQL |
|
389 | ||
390 |
# Time::Piece object to DATETIME format |
|
391 |
tp_to_datetime => sub { |
|
392 |
return shift->strftime('%Y-%m-%d %H:%M:%S'); |
|
393 |
} |
|
394 |
|
|
395 |
# Time::Piece object to DATE format |
|
396 |
tp_to_date => sub { |
|
397 |
return shift->strftime('%Y-%m-%d'); |
|
398 |
}, |
|
399 |
|
|
400 |
# DATETIME to Time::Piece object |
|
401 |
datetime_to_tp => sub { |
|
402 |
return Time::Piece->strptime(shift, '%Y-%m-%d %H:%M:%S'); |
|
403 |
} |
|
404 |
|
|
405 |
# DATE to Time::Piece object |
|
406 |
date_to_tp => sub { |
|
407 |
return Time::Piece->strptime(shift, '%Y-%m-%d'); |
|
408 |
} |
|
409 | ||
410 |
SQLite |
|
411 |
|
|
412 |
# Time::Piece object to DATETIME format |
|
413 |
tp_to_datetime => sub { |
|
414 |
return shift->strftime('%Y-%m-%d %H:%M:%S'); |
|
415 |
} |
|
416 |
|
|
417 |
# Time::Piece object to DATE format |
|
418 |
tp_to_date => sub { |
|
419 |
return shift->strftime('%Y-%m-%d'); |
|
420 |
}, |
|
421 |
|
|
422 |
# DATETIME to Time::Piece object |
|
423 |
datetime_to_tp => sub { |
|
424 |
return Time::Piece->strptime(shift, $FORMATS->{db_datetime}); |
|
425 |
} |
|
426 |
|
|
427 |
# DATE to Time::Piece object |
|
428 |
date_to_tp => sub { |
|
429 |
return Time::Piece->strptime(shift, $FORMATS->{db_date}); |
|
430 |
} |
|
431 |
|
|
added DBIx::Custom::Guides
|
432 |
=head2 6. Get high performance |
433 | ||
434 |
=head3 Use execute() method instead suger methods |
|
435 | ||
436 |
If you execute insert statement by C<insert()> method, |
|
437 |
you sometimes can't get required performance. |
|
438 | ||
439 |
C<insert()> method is a little slow because SQL statement and statement handle |
|
440 |
is created every time. |
|
441 | ||
442 |
In that case, you can prepare a query by C<create_query()> method. |
|
443 |
|
|
444 |
my $query = $dbi->create_query( |
|
remove DBIx::Custom::Model
|
445 |
"insert into book {insert_param title author};" |
added DBIx::Custom::Guides
|
446 |
); |
447 | ||
448 |
Return value of C<create_query()> is L<DBIx::Custom::Query> object. |
|
449 |
This keep the information of SQL and column names. |
|
450 | ||
451 |
{ |
|
remove DBIx::Custom::Model
|
452 |
sql => 'insert into book (title, author) values (?, ?);', |
added DBIx::Custom::Guides
|
453 |
columns => ['title', 'author'] |
454 |
} |
|
455 | ||
456 |
Execute query repeatedly. |
|
457 |
|
|
remove DBIx::Custom::Model
|
458 |
my $params = [ |
added DBIx::Custom::Guides
|
459 |
{title => 'Perl', author => 'Ken'}, |
460 |
{title => 'Good days', author => 'Mike'} |
|
461 |
]; |
|
462 |
|
|
remove DBIx::Custom::Model
|
463 |
foreach my $param (@$params) { |
464 |
$dbi->execute($query, $param); |
|
added DBIx::Custom::Guides
|
465 |
} |
466 | ||
467 |
This is faster than C<insert()> method. |
|
468 | ||
469 |
=head2 7. More features |
|
470 | ||
471 |
=head3 Get DBI object |
|
472 | ||
473 |
You can get L<DBI> object and call any method of L<DBI>. |
|
474 | ||
475 |
$dbi->dbh->begin_work; |
|
476 |
$dbi->dbh->commit; |
|
477 |
$dbi->dbh->rollback; |
|
478 | ||
479 |
=head3 Change Result class |
|
480 | ||
481 |
You can change Result class if you need. |
|
482 | ||
483 |
package Your::Result; |
|
484 |
use base 'DBIx::Custom::Result'; |
|
485 |
|
|
486 |
sub some_method { ... } |
|
487 | ||
488 |
1; |
|
489 |
|
|
490 |
package main; |
|
491 |
|
|
492 |
use Your::Result; |
|
493 |
|
|
494 |
my $dbi = DBIx::Custom->connect(...); |
|
495 |
$dbi->result_class('Your::Result'); |
|
496 | ||
add examples
|
497 |
=head3 Custamize query builder object |
added DBIx::Custom::Guides
|
498 | |
add examples
|
499 |
You can custamize query builder object |
added DBIx::Custom::Guides
|
500 | |
501 |
my $dbi = DBIx::Custom->connect(...); |
|
502 |
$dbi->query_builder->register_tag_processor( |
|
503 |
name => sub { |
|
504 |
... |
|
505 |
} |
|
506 |
); |
|
507 | ||
508 |
=head3 Resister helper method |
|
509 | ||
510 |
You can resiter helper method. |
|
511 | ||
512 |
$dbi->helper( |
|
513 |
update_or_insert => sub { |
|
514 |
my $self = shift; |
|
515 |
# do something |
|
516 |
}, |
|
517 |
find_or_create => sub { |
|
518 |
my $self = shift; |
|
519 |
# do something |
|
520 |
} |
|
521 |
); |
|
522 | ||
523 |
Register helper methods. |
|
524 |
These method can be called from L<DBIx::Custom> object directory. |
|
525 | ||
526 |
$dbi->update_or_insert; |
|
527 |
$dbi->find_or_create; |
|
528 | ||
add examples
|
529 |
=head2 EXAMPLES |
530 | ||
531 |
=head3 Limit clause |
|
532 | ||
533 |
my $rows = $dbi->select( |
|
534 |
table => 'table1', |
|
535 |
where => {key1 => 1}, |
|
536 |
append => "order by key2 {limit 1 0}" # {limit COUNT OFFSET} |
|
537 |
)->fetch_hash_all; |
|
538 | ||
539 |
SQLite |
|
540 | ||
541 |
$dbi->query_builder->register_tag_processor( |
|
542 |
limit => sub { |
|
543 |
my ($count, $offset) = @_; |
|
544 |
|
|
545 |
my $s = ''; |
|
546 |
$s .= "limit $count"; |
|
547 |
$s .= " offset $offset" if defined $offset; |
|
548 |
|
|
549 |
return [$s, []]; |
|
550 |
} |
|
551 |
); |
|
552 | ||
553 |
MySQL |
|
554 | ||
555 |
$dbi->query_builder->register_tag_processor( |
|
556 |
limit => sub { |
|
557 |
my ($count, $offset) = @_; |
|
558 |
|
|
559 |
my $s = ''; |
|
560 |
$offset = 0 unless defined $offset; |
|
561 |
$s .= "limit $offset"; |
|
562 |
$s .= ", $count"; |
|
563 |
|
|
564 |
return [$s, []]; |
|
565 |
} |
|
566 |
); |
|
567 | ||
added DBIx::Custom::Guides
|
568 |
=cut |