Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: perl-SQL-SplitStatement | Distribution: SUSE Linux Enterprise 15 SP4 |
Version: 1.00020 | Vendor: openSUSE |
Release: bp154.1.24 | Build date: Mon May 9 11:24:48 2022 |
Group: Development/Libraries/Perl | Build host: lamb60 |
Size: 104944 | Source RPM: perl-SQL-SplitStatement-1.00020-bp154.1.24.src.rpm |
Packager: https://bugs.opensuse.org | |
Url: http://search.cpan.org/dist/SQL-SplitStatement/ | |
Summary: Split any SQL code into atomic statements |
This is a simple module which tries to split any SQL code, even including non-standard extensions (for the details see the the /SUPPORTED DBMSs manpage section below), into the atomic statements it is composed of. The logic used to split the SQL code is more sophisticated than a raw 'split' on the ';' (semicolon) character: first, various different statement terminator _tokens_ are recognized (see below for the list), then this module is able to correctly handle the presence of said tokens inside identifiers, values, comments, 'BEGIN ... END' blocks (even nested), _dollar-quoted_ strings, MySQL custom 'DELIMITER's, procedural code etc., as (partially) exemplified in the the /SYNOPSIS manpage above. Consider however that this is by no means a validating parser (technically speaking, it's just a _context-sensitive tokenizer_). It should rather be seen as an in-progress _heuristic_ approach, which will gradually improve as test cases will be reported. This also means that, except for the the /LIMITATIONS manpage detailed below, there is no known (to the author) SQL code the most current release of this module can't correctly split. The test suite bundled with the distribution (which now includes the popular _Sakila_ and _Pagila_ sample db schemata, as detailed in the the /SHOWCASE manpage section below) should give you an idea of the capabilities of this module If your atomic statements are to be fed to a DBMS, you are encouraged to use the DBIx::MultiStatementDo manpage instead, which uses this module and also (optionally) offers automatic transactions support, so that you'll have the _all-or-nothing_ behavior you would probably want.
Artistic-1.0 or GPL-1.0+
* Tue Jan 27 2015 coolo@suse.com - regenerate spec to install LICENSE * Sat Aug 31 2013 egdfree@opensuse.org - add BuildRoot line in spec for correctly compile on SLE * Sun Aug 25 2013 egdfree@opensuse.org - initial
/usr/bin/sql-split /usr/lib/perl5/vendor_perl/5.26.1/SQL /usr/lib/perl5/vendor_perl/5.26.1/SQL/SplitStatement.pm /usr/lib/perl5/vendor_perl/5.26.1/x86_64-linux-thread-multi /usr/share/doc/packages/perl-SQL-SplitStatement /usr/share/doc/packages/perl-SQL-SplitStatement/Changes /usr/share/doc/packages/perl-SQL-SplitStatement/LICENSE /usr/share/doc/packages/perl-SQL-SplitStatement/README /usr/share/man/man1/sql-split.1.gz /usr/share/man/man3/SQL::SplitStatement.3pm.gz
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Jul 9 15:53:55 2024