Initial import of new posts
This commit is contained in:
parent
e4bafbb361
commit
0e12688f04
391 changed files with 14594 additions and 0 deletions
19
_posts/2007-12-28-qsql-vs-db-api.markdown
Normal file
19
_posts/2007-12-28-qsql-vs-db-api.markdown
Normal file
|
@ -0,0 +1,19 @@
|
|||
---
|
||||
author: einar
|
||||
comments: true
|
||||
date: 2007-12-28 12:58:40+00:00
|
||||
layout: post
|
||||
slug: qsql-vs-db-api
|
||||
title: QSql vs DB-API?
|
||||
wordpress_id: 358
|
||||
categories:
|
||||
- Linux
|
||||
tags:
|
||||
- Linux
|
||||
- programming
|
||||
- python
|
||||
---
|
||||
|
||||
I've recently begun trying to create GUIs for my Python applications with [PyQt](http://www.riverbankcomputing.co.uk/pyqt/index.php), and I can say I'm absolutely loving the toolkit, relatively easy to use and featureful. As I'm trying to create a GUI for some module I wrote that deals with databases (using MySQLdb), I also learnt that Qt has a series of classes for dealing with databases, mainly QSql.
|
||||
|
||||
My question, directed to whoever has experience with QSql and the Python DB-API, is: what are the advantages of one approach to the other? I'm leaning towards DB-API because like that I can create modules which work also in command line applications.
|
Reference in a new issue