Hi all,
I've been working with the improved e-commerce package that Bart
worked on (thanks Berklee College!) along with Janine (thanks for the
payflow pro module). I've bumped into some things that will require
changes to the package, so I'm bringing them to the community:
1) PostgreSQL 7.2 has milisecond precision on timestamps now. This
breaks some functionality that relies on Tcl's clock scan command. The
way to cope with that is to change the queries and the Tcl proc. But
to change the queries to the efficient way (using epoch) will break
the Oracle version.
The problem is that I don't have time right now to fix the Oracle
version (which I already broken, I hear). But I commit to do so in a
couple weeks.
2) The ec_financial_transactions table has creditcard payments hard
wired. For what I'm working on, that's not a good assumption since
we'll take Paypal and other forms of payment. The way to solve that
would be with another table (say ec_payment_map) that would map the
transaction_id to the id of whatever payment method (e.g.
creditcard_id, paypal_account_id, etc.) This would require changes to
3 .xql files. Not much I think.
The ugly way to do this without modifying the e-commerce datamodel
would be by creating a separate table for
paypal_financial_transactions, almost duplicating what's in
ec_financial_transactions, with the exception of the creditcard_id.
So what do people think about these issues? Is credit card-only an
assumption that we want to keep?
Thanks in advance.
