How to Install and Uninstall schemaspy Package on openSuSE Tumbleweed

Last updated: December 24,2024

1. Install "schemaspy" package

This tutorial shows how to install schemaspy on openSuSE Tumbleweed


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                schemaspy
            
                    
    
    Copied

2. Uninstall "schemaspy" package

Please follow the guidelines below to uninstall schemaspy on openSuSE Tumbleweed:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                schemaspy
            
                    
    
    Copied

3. Information about the schemaspy package on openSuSE Tumbleweed

Information for package schemaspy:
----------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : schemaspy
Version : 5.0.0-8.1
Arch : noarch
Vendor : openSUSE
Installed Size : 260.9 KiB
Installed : No
Status : not installed
Source package : schemaspy-5.0.0-8.1.src
Upstream URL : https://schemaspy.sourceforge.net/
Summary : Tool for analyzing and graphing database schemas
Description :
SchemaSpy is a Java-based tool that analyzes the metadata of a
schema in a database and generates a visual representation of it in a
browser-displayable format. It lets you click through the hierarchy of
database tables via child and parent table relationships as represented
by both HTML links and entity-relationship diagrams. It's also designed
to help resolve the obtuse errors that a database sometimes gives related
to failures due to constraints.
SchemaSpy uses JDBC's database metadata extraction services to gather the
majority of its information, but has to make vendor-specific SQL queries
to gather some information such as the SQL associated with a view and
the details of check constraints. The differences between vendors have
been isolated to configuration files and are extremely limited. Almost
all of the vendor-specific SQL is optional.