Package: ezodbc
ezodbcezodbc is a package built for anyone using pandas with a database. ezodbc aims to make it easier, smoother, and more secure to access databases via python by creating a SQLAlechemy engine object to facilitate the connection. and combining that with a GUI based on the tkinter library to provide a simple and intuitive way to enter the required information. Passwords, usernames, and other sensitive information is not saved anywhere (but potentially your own computer in a future release to bypass having to enter it each time). Below is a list of the databases and connectors supported.DatabaseODBC ConnectorMicrosoft SQL Serverpyodbc, pymssqlMySQLMySQLdbPostgrespsycopg2SQLitesqlite3InstallationTo install, you must have python 3.6+. Particularly, you will also needBuild Toolsinstalled for some odbc connector libraries, namely mysqlclient. If this gives you trouble, attempt to install those libraries individually as it may provide you with more context on a given issue.pip install ezodbcTo reduce installation overhead, ezodbc does not automatically download connectors for you. To use the library successfully and depending on what database you have, you must also install your desired python library for connecting to the database. Below are the options you have:Microsoft SQL Server:pip install pymssqlorpip install pyodbcMySQL:pip install mysqlclientPostgres:pip install psycopg2SQLite: sqlite3 is a python standard library. No need to pip install.Getting StartedThe purpose of ezodbc is to provide users with a more seamless experience with pandas while using a database connection to pull data, most often using thepd.read_sql()method to retrieve that data. When you connect to a database that other users are also in, you run the possibility of accidently creating some sort of issue within the database itself as well as accidentally exposing the database to risk by leaving user credentials and hostname information hard-coded. Before the only way to avoid that was with environment variables, which might be confusing to any newer programmers out there - but now there is another... ezodbc!An example of a simple use case, compared with that of regular useage of the connectors:importsqlalchemyimportpandasaspdfromezodbcimportez# both sql and timeout are optional with ezodbc - see belowdefwith_ezodbc()->pd.DataFrame:df=ez().run_query()returndfHOSTNAME='127.0.0.1:3306'# host:port ... another example would le my.database.local:3306 if there is a DNSDB='myDatabaseName'USER='my_username'PASSWORD='my_password'SQL="""SELECT * FROM [schema.tablename]"""TIMEOUT=60# This is pretty much the minimum you can get with the connectordefwithout_ezodbc(user:str,password:str,hostname:str,db_name:str,sql:str,timeout:int=30)->pd.DataFrame:connection_string='mysql://'+user+':'+password+'@'+hostname+'/'+db_nameengine=sqlalchemy.create_engine(connection_string,connect_args={'connect_timeout':30}})withengine.connect()asconnection:df=pd.read_sql(sql,connection)returndfDuring execution, you'll see a window pop-up for you to then enter the required information. The window looks like this:Fields & Their UsageThere are several selections and entries you must make to properly use ezodbc:Save Profile Toggle- Select whether to save this profile for future use or not. The file is store unencrypted in the users home directory (similar to that of AWS's boto3 and awscli's .aws configure file)Database Type (buttons on left)- This is to select the type of connector you'd like to use. The default is pymssql, which is the only one which requires the user to have aDomainfilled in.Domain- This is refering to the domain of a username. An example is CORP\brandon, where CORP\ is the domain. This can be left black in all cases but with the default, Microsoft SQL Server Free TDS.Username- username for access to the databasePassword- password for the username to authenticateDatabase Connection String- Host:Port ... in some cases, host will be an IP address, and sometimes it will have a DNS and appear as text.examples: 127.0.0.1:3306 and my.database.local:3306Database Name- the schema name or database name in the serverCopy/Paste SQL Query- the SQL Query you want to run. This is optional if you provide it in the constructor, ie df = ez.data(sql="give me your data plz, mr. database")Profiles"It gets annoying to type the information each time, I wish there were a way to easily recycle connection information!"... Do I have some good news for you!Profiles are useful if you would like to save the connection string for future use, and can do so on a secure machine. On the connection dialogue, simply specify that you would like to save the profile. The package will proceed to verify that your entered information is valid by trying to open a connection on the database. If the test connection succeeds, then the profile will be saved.Following entering your connection information, you will be prompted to save that connection string with a new prompt that asks for a profile name. That box will appear as the image below:The profiles are saved in your user home directory. That means it would be in a location likeC:/users/YOUR_USER_NAME/.ezodbc/profiles.toml. Feel free to delete it at any time given you would like to remove all connection strings.To use a previously saved profile, you can specify a profile_name in the ez constructor:fromezodbcimportez# Example assumes I have a "MyDatabase" profile in C:/users/YOUR_USER_NAME/.ezodbc/profiles.tomldf=ez(profile_name="MyDatabase",timeout=30).run_query()Query timeoutsYou can declare connection timeouts (seconds) for running your query. To do so, simply create the constructor with the optional "timeout=" parameter.fromezodbcimportezsql_query="""give me your data plz, mr. database"""df=ez(timeout=30).run_query(sql=sql_query)Planned EnhancementsBasic hashing for the connection string in profiles for added obfuscationAbility to declare more kwargs for connections. Currently only able to declare query timeoutAbility to delete user profiles