User login
Quick Help
SVN Commit Log
License Informaiton
SOPAC, Locum, and Insurge are made freely available under the GNU Public License v3
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License
Search
New forum topics
Recent comments
- Re:
4 weeks 1 day ago - thanks, very helpful info for
4 weeks 3 days ago - great article
4 weeks 3 days ago - It's indeed a good post
4 weeks 4 days ago - info
6 weeks 18 hours ago - UGG Boots Clearance
UGGS
7 weeks 4 days ago - Can't go to http://sopac/catalog
19 weeks 4 days ago - VMware Workstation or Server?
1 year 29 weeks ago - Did you create a file called
1 year 31 weeks ago - Sort of. We're using the
1 year 37 weeks ago



Josh,
In theory, Locum could work with postgres since it depends on PEAR::MDB2 which is DB agnostic. Though, I can't say with certainty at this point that all of the individual queries would work, since I didn't run them all via MDB2's prepare function. I'd say that that would be something to strive for.
Was it insufficient for your needs?
No, postgres is a great RDBMS and would work very well. I think the issue is that MySQL is far more ubiquitous and it is more likely that a library would have MySQL expertise in-house than postgres.
Sorry, it looks like my comment was cut in half. I was wondering if the drupal database abstraction layer was insufficient for your needs, since the intent is to make all drupal installations db agnostic.
Well, in general, I find that the Drupal DB API is a little sparse, especially compared to a full-blown DB class like MDB2. But that's not really germane. Locum and Insurge are software libraries that have nothing to do with Drupal and so wouldn't have the Drupal API available to them.