inconsistence of mailtrack_tbl

Use this forum for all questions related to the source code of OpenEMM

Moderator: moderator

sfantul
Posts: 40
Joined: Tue Aug 15, 2006 9:34 am

inconsistence of mailtrack_tbl

Post by sfantul » Tue Dec 05, 2006 2:07 pm

changes u made for permiting only one company for the the open source version i think generated an inconsistency on mailtrack_tbl
on one hand u use this table for counting the mails that were sent on a mailing

Code: Select all

            String	query = "INSERT INTO " + data.mailtracking_table + " " +
                    "(company_id, status_id, mailing_id, customer_id) " +
                    "SELECT " + data.company_id + ", " + data.maildrop_status_id + ", " + data.mailing_id + ", cust.customer_id " +
                    get_fromclause () + " " +
                    get_whereclause (true);
data.maildrop_status_id is the status_id from the maildrop_status_tbl (so can have also values like 90,100 )

and u also use it in the softbounce script

Code: Select all

iquery = 'INSERT INTO mailtrack_tbl (customer_id, company_id, mailing_id, status_id, change_date) '
	iquery += 'VALUES (:customer, :company, :mailing, 90, now())'
then in the softbounce script some deletions are done ...

This does not seem OK. Am i wrong?

ud
Posts: 141
Joined: Thu Aug 17, 2006 9:56 am
Location: Munich, Germany
Contact:

Post by ud » Tue Dec 19, 2006 2:30 pm

I'm afraid, you are right. The softbounce script seems to have some problems, so better don't use it in this version, a new release will have a reworked version.

-- ud

sfantul
Posts: 40
Joined: Tue Aug 15, 2006 9:34 am

Post by sfantul » Fri Feb 09, 2007 5:56 pm

For the mailtrack_tbl issue wouldn't be a workaround , until the next version , to create another table (e.g. mailtrack_soft_tbl) with same fields as mailtrack_tbl and replace all occurrences of the mailtrack_tbl with the new one only in softbounce.py?
Actually my question is if this table needed by softbounce.py is used anywhere else.

Post Reply