Re: abstraction for databases

Manuel Lemos wrote: > For instance, if you want to handle fields with dates, unlike Metabase, > those other packages do not guarantee that the date values always go > formatted in the same standard: ISO 8601 (YYYY-MM-DD). With Metabase you > can definitely write database independent applications. I like the idea of metabase, but it misses some vital functions. For example, what about references? Transactions? Then there is the code...the code is to damned packed for me to bother, I haven't had the time to make it adhere to something I'm comfortable to read. I'd love to use Metabase, but since I can't support references, I'm at square one. (Hey, I happen to like them.) A question, PEAR, which I've heard of, do you know if it just wraps functions into a standard layer, or does it provide more in the way of Metabase? -- Paul K Egell-Johnsen Developer/PR Manager zez.org: about code zez.org