* Wietse Venema <postfix-users@postfix.org>: > Victor Duchovni: > > On Fri, Jun 18, 2010 at 05:58:02PM +0200, Patrick Ben Koetter wrote: > > > > > > Right now this is a read-only implementation (like mysql/pgsql) > > > > but it may be worthwhile to add update support. SQLite implements > > > > locking internally. That would allow us to avoid the problems with > > > > Postfix's external locks on Berkeley DB maps, which are broken > > > > after BDB version 2. > > > > > > That's great news! > > > > Indeed. One still needs tools to insert data into the database. > > Does Postfix need to provide a minimal interface for this, or do we > > assume that SQLite users will have adequate tools outside Postfix. > > A "postmap" option to create an SQLite file would make sense.
Do you mean creating an SQLite database from a flat file that, for example, contains access rules mapping addresses to actions (r...@foo REJECT)? What if there were many files that wanted to be stored in a SQLite database? Creating a database only for one table would be a waste of ressources, I guess. Would it make sense to have two commands? One to create the database and one to add flat files as tables to the database or update existing tables? Or do you mean only creating a database and then use other tools to maintain the data therein? The easiest part - assuming the SQLite driver can also write - would probably be to use it on everything that goes into $data_directory i.e. databases that keep track of tls session keys or verified senders and so on. p...@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>
