Skip to main content

How to connect SQLite database using Python?

To connect to an SQLite database from Python, you can use the sqlite3 module, which is part of the Python Standard Library. To create a connection to an SQLite database, you can use the connect() method of the sqlite3 module, passing it the path to the database file. Here is an example:

import sqlite3

# create a connection to the database
conn = sqlite3.connect('my_database.db')

# create a cursor object that can be used to execute SQL statements
cursor = conn.cursor()

# execute a SQL query
cursor.execute('SELECT * FROM my_table')

# get the results of the query as a list of records
results = cursor.fetchall()

# loop through the results and print each record
for row in results:

# close the connection to the database

This code assumes that you have an SQLite database file called my_database.db that contains a table called my_table. This code also assumes that you have the necessary permissions to read and write to the database file. You can use the cursor object to execute any other SQL queries you need, such as INSERT, UPDATE, or DELETE.


Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are,, respectively. Proper communication with other servers on the network we should use routing tables. There are three

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) Slave1 Node: (Centos 7.2) Slave2 Node: (Centos 7.2) Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/ Each Node: /etc/