How to Install and Uninstall perl-SQL-SplitStatement Package on openSUSE Leap

Last updated: June 17,2024

1. Install "perl-SQL-SplitStatement" package

In this section, we are going to explain the necessary steps to install perl-SQL-SplitStatement on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-SQL-SplitStatement
            
                    
    
    Copied

2. Uninstall "perl-SQL-SplitStatement" package

Please follow the step by step instructions below to uninstall perl-SQL-SplitStatement on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-SQL-SplitStatement
            
                    
    
    Copied

3. Information about the perl-SQL-SplitStatement package on openSUSE Leap

Information for package perl-SQL-SplitStatement:
------------------------------------------------
Repository : Main Repository
Name : perl-SQL-SplitStatement
Version : 1.00020-bp155.2.8
Arch : noarch
Vendor : openSUSE
Installed Size : 102.5 KiB
Installed : No
Status : not installed
Source package : perl-SQL-SplitStatement-1.00020-bp155.2.8.src
Upstream URL : http://search.cpan.org/dist/SQL-SplitStatement/
Summary : Split any SQL code into atomic statements
Description :
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.