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

Last updated: November 23,2024

1. Install "perl-SQL-Translator" package

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


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-SQL-Translator
            
                    
    
    Copied

2. Uninstall "perl-SQL-Translator" package

This tutorial shows how to uninstall perl-SQL-Translator on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-SQL-Translator
            
                    
    
    Copied

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

Information for package perl-SQL-Translator:
--------------------------------------------
Repository : Main Repository
Name : perl-SQL-Translator
Version : 1.62-bp155.2.10
Arch : noarch
Vendor : openSUSE
Installed Size : 3.3 MiB
Installed : No
Status : not installed
Source package : perl-SQL-Translator-1.62-bp155.2.10.src
Upstream URL : https://metacpan.org/release/SQL-Translator
Summary : Manipulate structured data definitions (SQL and more)
Description :
This documentation covers the API for SQL::Translator. For a more general
discussion of how to use the modules and scripts, please see
SQL::Translator::Manual.
SQL::Translator is a group of Perl modules that converts vendor-specific
SQL table definitions into other formats, such as other vendor-specific
SQL, ER diagrams, documentation (POD and HTML), XML, and Class::DBI
classes. The main focus of SQL::Translator is SQL, but parsers exist for
other structured data formats, including Excel spreadsheets and arbitrarily
delimited text files. Through the separation of the code into parsers and
producers with an object model in between, it's possible to combine any
parser with any producer, to plug in custom parsers or producers, or to
manipulate the parsed data via the built-in object model. Presently only
the definition parts of SQL are handled (CREATE, ALTER), not the
manipulation of data (INSERT, UPDATE, DELETE).