Aquatic Prime: Add MySQL support

[GoogleCodeExporter]

It would be really nice if Aquatic Prime's server-side code included support 
for writing generated 
registration information to MySQL (or some other database).

I added this in my local copy of AP, and changes are attached.  This adds 
support only for 
eSellerate, since that's what I'm using.  I'm not at all certain it should be 
committed to trunk as-is 
because at present it assumes you'll be using a database.  If you don't get a 
MySQL connection, it 
bails out.  However it may be useful as a starting point.

The attached patch modifies AquaticPrimeEsellerate.php, Config.php, and 
eSellerateXML.php.  
SQL code supporting this is in eSellerate.sql.

Original issue reported on code.google.com by atomicb...@gmail.com on 23 Jul 2007 at 9:40

Attachments:

• mysql.patch
• eSellerate.sql

[GoogleCodeExporter]

Can you ping Lucas on this to get him to review it?

Original comment by cforsy...@gmail.com on 3 Sep 2007 at 5:19

[GoogleCodeExporter]

This is now in svn.

Original comment by lllu...@gmail.com on 3 Sep 2007 at 6:05

[GoogleCodeExporter]

Marking as fixed.

Original comment by lllu...@gmail.com on 3 Sep 2007 at 6:07

• Changed state: Fixed

[GoogleCodeExporter]

Just in case someone needs to know this for later, this was added in revision 
193, thanks Tom and Lucas!

Original comment by cforsy...@gmail.com on 3 Sep 2007 at 6:33

[GoogleCodeExporter]

It doesn't look like eSellerate.sql was added, which is necessary to make use 
of the new PHP code.  I added that 
in rev 210.

Original comment by atomicb...@gmail.com on 6 Sep 2007 at 11:19