Thanks for the reply PGF. Some more searches here revealed Gman's DBMS wrapper code. It looks like it supplies a nice independent interface to both MySQL and PostgreSQL, so choosing one or the other at this point won't be much of an issue.
I need to give a big thanks to Gman for the module!
Regarding performance issues, I suppose you're right. I have a bad habit of fearing that the KISS solution will be too slow and end up trying to search out and implement systems that are far too advanced for my current skill level and then get discouraged by the lack of progress and end up giving up. Baby steps, baby steps. I think I'll just go ahead with MySQL for the moment only because I've got some documentation on it and it seems simpler than PostgreSQL. Early on during the implementation of the spatial handling code I'll test the hell out of it, and if I actually run up against performance barriers I'll make a switch.
I need to give a big thanks to Gman for the module!
Regarding performance issues, I suppose you're right. I have a bad habit of fearing that the KISS solution will be too slow and end up trying to search out and implement systems that are far too advanced for my current skill level and then get discouraged by the lack of progress and end up giving up. Baby steps, baby steps. I think I'll just go ahead with MySQL for the moment only because I've got some documentation on it and it seems simpler than PostgreSQL. Early on during the implementation of the spatial handling code I'll test the hell out of it, and if I actually run up against performance barriers I'll make a switch.