Ok. But without postgres support, I can't release 2.0.8 *with* this patch.
new patch version with postgres support is attached
it's seems to work for me on my simple postgres installation :)
--
Regards,
Eugene Prokopiev
--- ./pipe.c.orig 2005-08-19 18:30:42 +0400
+++ ./pipe.c 2005-09-20
Eugene Prokopiev wrote:
Ok. But without postgres support, I can't release 2.0.8 *with* this
patch.
new patch version with postgres support is attached
it's seems to work for me on my simple postgres installation :)
Did you change anything other than the postgres sql? Because for
Paul J Stevens wrote:
Eugene Prokopiev wrote:
Ok. But without postgres support, I can't release 2.0.8 *with* this
patch.
new patch version with postgres support is attached
it's seems to work for me on my simple postgres installation :)
Did you change anything other than the postgres
Eugene Prokopiev wrote:
Paul J Stevens wrote:
Eugene,
I've included your patch as a dpatch in the debian packages.
I fixed a couple of compiler warnings in db_get_mailbox_from_filters,
but other than that, things are unchanged.
Did you move db_get_mailbox_from_filters function into
Eugene,
I've included your patch as a dpatch in the debian packages.
I fixed a couple of compiler warnings in db_get_mailbox_from_filters,
but other than that, things are unchanged.
This still needs a postgres version of the table.
I've only done a debian/unstable upload. Stable will follow
Jesse Norell wrote:
My filtering algorithm:
1) Read all filtering rules for current user with SELECT filter_field,
filter_value, mailbox FROM dbmail_filters WHERE user_id = '%llu' ORDER
BY filter_id
2) For every record read all mail headers and compare it with current
record in
Eugene Prokopiev wrote:
I hope my code will merged with mail DBMail source tree so anybody will
can use my code or change it. But I haven't answer in dbmail-dev
maillist about my patch.
Sometimes I have to make a living :-)
I know that adding new features in stable version is not good
I like it. I am probably going to put it on my backup server and try it
as a alternative install... Just to try it out. It would save me a lot
of trouble with running Evolution and Filters. I am no dev but i think
it looks good.
One idea, what about using an enum on the filter_field column
Steven Lynn wrote:
I was able to compile it in with your patch and I added the table to the
database. However, I think I am doing something wrong because cause I
can not seem to get it to filter. I turned up TRACE_LEVEL (5) but not
sure if I have it up high enough because I do not even see
Steven Lynn wrote:
I like it. I am probably going to put it on my backup server and try it
as a alternative install... Just to try it out. It would save me a lot
of trouble with running Evolution and Filters. I am no dev but i think
it looks good.
One idea, what about using an enum on the
My filtering algorithm:
1) Read all filtering rules for current user with SELECT filter_field,
filter_value, mailbox FROM dbmail_filters WHERE user_id = '%llu' ORDER
BY filter_id
2) For every record read all mail headers and compare it with current
record in dbmail_filters.
3)
11 matches
Mail list logo