Installation
Setting up Masonite is extremely simple.
If you are using the Masonite web framework than all the installation is setup for you. If you are using anything other than Masonite or building your own Python application then be sure to follow the install steps below:
Pip install
First install via pip:
Configuration File
To start configuring your project you'll need a config/database.py
file. In this file we will be able to put all our connection information.
One we have our config/database.py
file we can put a DATABASES
variable with a dictionary of connection details. Each key will be the name of our connection. The connection name can be whatever you like and does not need to relate to a database name. Common connection names could be something like dev
, prod
and staging
. Feel free to name these connections whatever you like.
The connection variable will look something like this
Lastly you will need to import the ConnectionResolver
class and and register the connection details. Normal convention is to set this to a variable called DB
:
After this you have successfully setup Masonite ORM in your project!
MSSQL
Masonite ORM supports Microsoft SQL Server and several options to modify the connection string. All available options are:
Transactions
You can use global level database transactions easily by importing the connection resolver class:
You can then either rollback or commit the transactions:
You may also optionally pass the connection you'd like to use:
You can also use the transaction as a context manager:
If there are any exceptions in inside the context then the transaction will be rolled back. Else it will commit the transaction.
Logging
If you would like, you can log any queries Masonite ORM generates to any supported Python logging handler. First you need to enable logging in config/database.py
file through the log_queries
boolean parameter.
Inside your config/database.py
file you can put on the bottom here. The StreamHandler will output the queries to the terminal.
You can specify as many handlers as you would like. Here's an example of logging to both the terminal and a file:
Raw Queries
You can query the database directly using the connection resolver class. If you set the connection resolver to the variable DB
you can import it like:
You may also pass query bindings as well to protect against SQL injection by passing a list of bindings:
This will use the default connection but you may also optionally pass a connection to use:
Last updated