>>> Aahz wrote > Unlike Guido, I do already know SQL, so my preference is for SQL, but if > there's a clear/simple API for getting reports that has all the power of > SQL, that's fine with me. Note specifically that I'm not a fan of > mixing and matching languages for data manipulation. I do a _lot_ of SQL (ask Richard, he gets to hear me swear about it at work), but I'm not hung up on it. I don't know that it's a showstopper. Note that initially, at least, it would be far easier to work with and modify a hyperdb-based schema til it's "right", then, if performance/ reporting/whatever needed it, move to a relational backend. Anthony -- Anthony Baxter <anthony@interlink.com.au> It's never too late to have a happy childhood.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4