Well, the uc_payment_credit table is deprecated. I'll be removing it altogether when we move on to 2.0. The main reason is that there's no good reason to ever query against a CC table except to load data up with an order. Furthermore, I was having to encrypt, store, and decrypt the various fields separately. Since the order object has a data array that automatically gets serialized/saved and loaded/unserialized with the order, it just made sense to move the data. It wouldn't be feasible to try and handle saving/loading differently for normal and debug modes.
Re: Re: Changes coming to improve CC security
Fri, 05/23/2008 - 14:07
#1
Re: Re: Changes coming to improve CC security
Changes coming to improve CC security By: Ryan (9 replies) Tue, 05/13/2008 - 15:35
- Ryan wrote:
I'll be writing By: Blackguard (12/19/2008 - 13:50)
- Re: Ryan wrote: I'll be writing By: Ryan (12/19/2008 - 14:07)
- Re: Changes coming to improve CC security By: webmasterkai (05/23/2008 - 13:49)
- Re: Re: Changes coming to improve CC security By: Ryan (05/23/2008 - 14:07)
- Re: Changes coming to improve CC security By: torgosPizza (05/13/2008 - 15:49)
- Re: Re: Changes coming to improve CC security By: Ryan (05/14/2008 - 10:27)
- *sigh* while I agree that By: japerry@drupal.org (05/14/2008 - 17:54)
- Re: *sigh* while I agree that By: Ryan (05/15/2008 - 08:59)
- Re: Re: *sigh* while I agree that By: Ryan (05/15/2008 - 17:31)
- Re: *sigh* while I agree that By: Ryan (05/15/2008 - 08:59)
- *sigh* while I agree that By: japerry@drupal.org (05/14/2008 - 17:54)
- Re: Re: Changes coming to improve CC security By: Ryan (05/14/2008 - 10:27)
