I've been testing the SpamFilter software on an internal basis using SQL Server as the quarantine database engine.  I'm looking at suggesting this product to one of my clients and I developed some software for.  We're currently using VistaDB in their .NET applications because of the cost / licensing / ease of deployment, etc...

I know that this is not one of the supported database, but I gave it a try and I ported the SQL Server schema to VistaDB using their data migration tool.  I'm using an OLEDB provider that is supplied by VistaDB.  I have it working with Spam Filter with a couple of exceptions.  Complaints that a non-nullable column cannot be updated to null when a message arrives.  The only non-nullable field is the primary key which is auto incrementing.  Any suggestions?

Since this isn't a supported DB, I understand if you might not be able to help much on it.  I was wondering if you would consider supporting VistaDB in the future.  It's a really nice database engine.

Thanks,

George

Thanks for the response.  I had 3 errors originally, but have since resolved one of them by manually updating the database.  I think that if I remove one of these entries and the system attempts to add it back, it'll generate an error again.

05/30/06 00:02:01:593 -- Adding default Reject Codes: Domain is in local blacklist file
05/30/06 00:02:01:609 -- Error updading/checking tblRejectCodes - Non-nullable column cannot be updated to Null
05/30/06 00:02:01:625 -- Adding default Reject Codes: EmailFrom is in local blacklist file
05/30/06 00:02:01:640 -- Error updading/checking tblRejectCodes - Non-nullable column cannot be updated to Null
05/30/06 00:02:01:656 -- Adding default Reject Codes: Reverse DNS not found
05/30/06 00:02:01:671 -- Error updading/checking tblRejectCodes - Non-nullable column cannot be updated to Null
05/30/06 00:02:01:687 -- Adding default Reject Codes: Empty Mail From

The other two that I see in the logs are related to the quarantine table.  I notice that tblMsgs has nothing in it and nor does the tblQuarantine.  I assume the later has something to do with the following error(s).

Error that appears throughout the log:

05/31/06 23:24:25:904 -- (304) Blacklist cache - starting cleanup
05/31/06 23:24:25:904 -- (2576) Exception occurred during TDeleteExpiredQuarantineThread.Execute: Error code: 573 Syntax Error:   syntax error at line : 1, Column: 7, token: DISTINCTROW Error code: 610 OpenSQL:  Error:573
Syntax Error:   syntax error at line : 1, Column: 7, token: DISTINCTROW
05/31/06 23:24:25:920 -- (1696) TBayesianThread - Begin LoadFromFile for corpus.db (db.dat)

Error that appears when an item is being quarantined:

05/30/06 03:25:55:092 -- (4004) - Reverse DNS not found -
05/30/06 03:25:55:092 -- (4004) 203.177.239.248 - Mail from: mailto:tknopp@mccauley.textron.com - tknopp@mccauley.textron.com To: mailto:george.peters@daytasystems.com - george.peters@daytasystems.com will be rejected
05/30/06 03:26:07:951 -- (4004) Error occurred during RECEIVEMESSAGE when accessing the quarantine database: Non-nullable column cannot be updated to Null ( 1 2 2b 3 3a 4 5 6 7 8 9 11 12 13 15 16 17 18 19 29 30 31 32 33 54 55 56 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91)
05/30/06 03:26:07:967 -- (4004) EMail from mailto:tknopp@mccauley.textron.com - tknopp@mccauley.textron.com to mailto:george.peters@daytasystems.com - george.peters@daytasystems.com was received and quarantined. Size: 1 KB, 1024 bytes
05/30/06 03:26:08:014 -- (2560) Time to add Msg to Bayes corpus:0

Thanks for any suggestions that you might have to offer.  I'm using an OLEDB connection:

Provider=VistaDBOLEDB20.VistaDBOLEDB;Database Name="C:\Program Files\SpamFilter\Database\SpamFilter.vdb".

Of course, without the database engine, it would be difficult for you to do anything.  The engine consists of 1 db file and for the OleDB, just 2 supporting DLLs.  Deploying with .NET requires no additional DLL.  That's one of the features I liked about this DB engine, very small footprint and easy to deploy/backup.  Supports encryption, etc.

I have a feeling it's related to the identiy column.  I have used this engine before in a C# project that could toggle between SQL Server and VistaDB.  I've never run into a problem with the identity value, then again I wasn't doing anything special.

Thanks again,

George

Of course, without the database engine, it would be difficult for you to do anything.  The engine consists of 1 db file and for the OleDB, just 2 supporting DLLs.  Deploying with .NET requires no additional DLL.  That's one of the features I liked about this DB engine, very small footprint and easy to deploy/backup.  Supports encryption, etc.

I have a feeling it's related to the identiy column.  I have used this engine before in a C# project that could toggle between SQL Server and VistaDB.  I've never run into a problem with the identity value, then again I wasn't doing anything special.