At some point when I have a lot of free time, I might consider downloading all the data and storing it in a database, but I'd need a lot of free time to want to do that. I wouldn't take a long time, it's just not that useful. Of all the things I could do with my time, making my own database for all of this doesn't get that high on my list. ;)
I'm not going to need to do fancy selects. Most records have no relationship to other records, and it's very easy to pull up a single record. I already get summary reports about total charges, etc, so I don't need that. Authorize.Net has the basic stuff covered. I just needed something a little different this time. If I did this in DBI, I would have taken a lot more time and had to write a lot more code. There's not a big gain there.
The interesting stuff is already in my subscriber database. That's where I can do nifty things, should I get the time. That is a relational database. :)
And I'm not attributing anything to malice: it's greed. :)
In reply to Re^2: Perl, Authorize.Net, and Broken Kneecaps
by brian_d_foy
in thread Perl, Authorize.Net, and Broken Kneecaps
by brian_d_foy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |