From: Richard T. <r.t...@er...> - 2004-01-14 08:45:01
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi I have just started to help out on a photo management application called io= ta.=20 The first task I am look at is moving the current Berkely database backen t= o=20 a more 'full featured' database. Sqlite is looking like a good fit.=20 My current dilemma is whether to interface directly with sqlite or instead = to=20 use the Qt database interface and use qsqlite. This would provide for addin= g=20 support for other, larger, databases later but raises some concerns in my=20 mind. I am not new to programming or to databases but I am new to Qt and sqlite, = so=20 bear with me if I sound a little nieve. On with the questions... 1) How mature / stable is qsqlite? I don't mind helping to stablise it, I j= ust=20 want to get a feel for what I am letting myself in for. 2) qsqlite is not currently part of the main distros (at least not Gentoo=20 which is my development platform). What would our app need to do at install= =20 time to make qsqlite available? Is it possible to install qsqlite just for= =20 use with one app or is there a separate 'system wide' install that the user= =20 would need to perform? Is it possible to package qsqlite along with the app= =20 if needed? I am concerned that the install process should remain as simple = as=20 possible or at least as simple as it is with the existing Berkeley database. 3) From what I understand about sqlite, the user does not need to perform a= ny=20 initialisation steps prior to an app making use of the database and there a= re=20 no 'username, password' issues for the user to deal with. Is this true for= =20 qsqlite as well?=20 I hope these questions make sense. Deciding on a database interface approac= h=20 is a tricky decision and will have long lasting implications for the intern= al=20 architecture of the app, so I hope you don't mind me asking these questions= =2E=20 Many thanks. Richard =2D --=20 Jabber: Ric...@ja... PGPKey: http://search.keyserver.net:11371/pks/lookup?op=3Dget&search=3D0xA7= DA9FD9 Key fingerprint =3D D051 A121 E7C3 485F 3C0E 1593 ED9E D868 A7DA 9FD9 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFABQAo7Z7YaKfan9kRAjHwAJ41ZdOjcEIGcJPUtHKh8ivBQ9RqvQCZAWPo lBPdtRtdwfN3YB8x9ymVfXw=3D =3D1sIR =2D----END PGP SIGNATURE----- |