Sorry about the confusion.
dbmail now appears to work; I've been able to inject messages into
dbmail and fetch them just fine.
Will do more testing... expect more patches!
--
Internet Connection High Quality Web Hosting
http://www.internetconnection.net/
diff -u -r1.2 dbsqlite.c
--- sqlite/dbsq
This is the corrected patch:
--- sqlite/dbsqlite.c 2005/02/18 21:33:25 1.2
+++ sqlite/dbsqlite.c 2005/02/18 22:03:47
@@ -172,8 +172,8 @@
{
unsigned long did = 0;
while (length > 0) {
- if (*from == '\'') *to++ = *from;
- *to++ = *from;
+
On Fri, 2005-02-18 at 22:54 +0100, Paul J Stevens wrote:
> Garn,
>
> Patch applied and create file added to cvs.
>
> CVS diffs are a pain though. Please provide unified diffs I you can.
Very well.
> There's also a char * buffer problem with insertion.
I see it now; must have missed a :w somepl
Geo Carncross wrote:
On Fri, 2005-02-18 at 17:16 +0100, Paul J Stevens wrote:
Geo Carncross wrote:
On Fri, 2005-02-18 at 10:27 +0100, Paul J Stevens wrote:
Geo,
I've added your dbsqlite.c to cvs-head in a separate directory. I've also added
sqlite to the autoconf files. Dbmail compiles j
Garn,
Patch applied and create file added to cvs.
CVS diffs are a pain though. Please provide unified diffs I you can.
There's also a char * buffer problem with insertion.
./dbmail-users -f /etc/dbmail/dbmail.conf -a testuser
Adding user testuser with password type ,0 bytes mailbox limit and
This is what I have so far; it is based off the MySQL one, but because
SQLite uses triggers to simulate uniqueness, and uses a postgres-like
create index format, I use those.
I'm considering adding support for DROP/IF by setting a trigger on
sqlite_master, but I'm sure that'll look like line noise
current_timestamp() is needed on sqlite.
current_timestamp() works on mysql
current_timestamp() does NOT work on postgresql (well, at least, not on
all versions)
this patch adds a SQL_CURRENT_TIMESTAMP parameter, fixes db.c to use it,
the debian patch and the sqlite driver.
This also includes a f
On Fri, 2005-02-18 at 17:16 +0100, Paul J Stevens wrote:
>
> Geo Carncross wrote:
> > On Fri, 2005-02-18 at 10:27 +0100, Paul J Stevens wrote:
> >
> >>Geo,
> >>
> >>I've added your dbsqlite.c to cvs-head in a separate directory. I've also
> >>added
> >>sqlite to the autoconf files. Dbmail compi
Geo Carncross wrote:
On Fri, 2005-02-18 at 10:27 +0100, Paul J Stevens wrote:
Geo,
I've added your dbsqlite.c to cvs-head in a separate directory. I've also added
sqlite to the autoconf files. Dbmail compiles just fine with sqlite support.
sqlite/Makefile.in wasn't included in CVS; my au
On Fri, 2005-02-18 at 10:27 +0100, Paul J Stevens wrote:
> Geo,
>
> I've added your dbsqlite.c to cvs-head in a separate directory. I've also
> added
> sqlite to the autoconf files. Dbmail compiles just fine with sqlite support.
sqlite/Makefile.in wasn't included in CVS; my autoconf/automake ch
Geo,
I've figured it out myself. I suppose the db parameter can and must be a path.
I've converted the mysql create_tables script to sqlite, but dbmail-imapd won't
run just yet :-(
Paul J Stevens wrote:
Paul J Stevens wrote:
Geo,
I've added your dbsqlite.c to cvs-head in a separate di
Paul J Stevens wrote:
Yep.
[EMAIL PROTECTED]:~$ file /tmp/dbmail.conf
/tmp/dbmail.conf: ASCII English text, with CRLF line terminators
Please strip those pesky linefeeds from the config. See if that helps.
Duh, read carriage-return stead of linefeed.
--
___
Yep.
[EMAIL PROTECTED]:~$ file /tmp/dbmail.conf
/tmp/dbmail.conf: ASCII English text, with CRLF line terminators
Please strip those pesky linefeeds from the config. See if that helps.
Dululu Ululu wrote:
On Fri, 18 Feb 2005 10:34:49 +0100, Paul J Stevens <[EMAIL PROTECTED]> wrote:
Your confi
On Fri, 18 Feb 2005 10:34:49 +0100, Paul J Stevens <[EMAIL PROTECTED]> wrote:
> Your config file is messed up I think. Show me please. The config parser for
> 2.0
> is very picky.
Attached
>
> [EMAIL PROTECTED] wrote:
> > The following bug has been SUBMITTED.
> > ==
Paul J Stevens wrote:
Geo,
I've added your dbsqlite.c to cvs-head in a separate directory. I've
also added sqlite to the autoconf files. Dbmail compiles just fine with
sqlite support.
Some things come to mind:
we need a create_tables file for sqlite?
where will we store the database file
Your config file is messed up I think. Show me please. The config parser for 2.0
is very picky.
[EMAIL PROTECTED] wrote:
The following bug has been SUBMITTED.
==
http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=00
Geo,
I've added your dbsqlite.c to cvs-head in a separate directory. I've also added
sqlite to the autoconf files. Dbmail compiles just fine with sqlite support.
Some things come to mind:
we need a create_tables file for sqlite?
where will we store the database file? /var/lib/sqlite/ would b
The following bug has been SUBMITTED.
==
http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=175
==
Reported By:dululu
Assigned To:
I've cobbled together what I think is 80-90% support for an SQLite
driver.
I'd like some assistance getting it into CVS and getting the various
autoconf nonsense set up so it doesn't depend on postgres/mysql.
I have not tested it yet, so perhaps the best thing to do is to setup a
way that we can
19 matches
Mail list logo
