select 'drop function ' || object_name from user_procedures where object_type = 'FUNCTION' union all select 'drop procedure ' || object_name from user_procedures where object_type = 'PROCEDURE' union all select 'drop sequence ' || sequence_name from user_sequences union all select 'drop view ' || view_name from user_views union all select 'drop table ' || table_name || ' cascade constraints' from user_tables union all select 'drop package ' || object_name from user_procedures where object_type = 'PACKAGE'
NAME
SQL::Exec::Oracel - Specific support for the DBD::SQLite DBI driver in SQL::Exec
SYNOPSIS
use SQL::Exec::SQLite;
SQL::Exec::SQLite::connect('/tmp/my.db');
DESCRIPTION
The SQL::Exec::SQLite
package is an extension of the SQL::Exec
package. This mean that in an OO context SQL::Exec::SQLite
is a sub-classe of SQL::Exec
(so all method of the later can be )and an extension
CONSTRUCTOR
The new
constructor of the
FUNCTIONS
This is a list of the public function of this library. Functions not listed here are for internal use only by this module and should not be used in any external code unless .
All the functions described below are automatically exported into your package except if you explicitely request to opposite with use Test::Subs ();
.
Finally, these function must all be called from the top-level and not inside of the code of another test function. That is because the library must know the number of test before their execution.
connect
test { CODE };
test { CODE } DESCR;
This function register a code-block containing a test. During the execution of the test, the code will be run and the test will be deemed successful if the returned value is true
.
The optionnal DESCR
is a string (or an expression returning a string) which will be added as a comment to the result of this test. If this string contains a printf
conversion (e.g. %s
or %d
) it will be replaced by the result of the code block. If the description is omitted, it will be replaced by the filename and line number of the test. You can use an empty string ''
to deactivate completely the output of a comment to the test.
test
todo { CODE };
todo { CODE } DESCR;
This function is the same as the function test
, except that the test will be registered as to-do. So a failure of this test will be ignored when your test is run inside a test plan by Test::Harness
or Tap::Harness
.
BUGS
Please report any bugs or feature requests to bug-dbix-puresql@rt.cpan.org
, or through the web interface at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=DBIx-PureSQL.
SEE ALSO
AUTHOR
Mathias Kende (mathias@cpan.org)
VERSION
Version 0.01 (January 2013)
COPYRIGHT & LICENSE
Copyright 2013 © Mathias Kende. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.