On Tue, Mar 26, 2013 at 11:57 PM, Guy Waterval <waterval....@gmail.com>wrote:
> Hi Andrew, > Hi all, > > 2013/3/27 Andrew Douglas Pitonyak <and...@pitonyak.org> > > > > > I like an embedded DB for those times that I desire a small DB for small > > data that is relational. For larger data sets, the embedded DB is > > insufficient. > > > > Indeed, end users and a lot of little structures could take profit of a > little DB easy to use, ie associations, sport clubs, TPE, museums, schools, > restaurants, little hotels, storekeepers, etc. Moreover, you can transform > the weakpoint in a marketing argument : why wearing shoes 45 if my size is > 40? > > A+ > -- > gw > My opinion is that users and AOO would be better served if users chose and installed their own small DB (one that would support some typical connectivity -- ODBC, JDBC) instead of AOO supplying one with the product. Many such good small scale DBs exist. It just seems to me that no matter what we have/choose now as an embedded DB, and problems that may ensue with it, and therefore might require future replacement, is a continual problematic cycle we really don't need. At this point, given that we don't really know what folks re doing with Base. I think it would be better to do a transitional move -- take out the embedded DB and therefore "Create new DB" option would go away. Let the front-end stuff alone. Naturally, we would have to investigate some export mechanisms for users, etc to preserve the data they may already have in ODB. > > > > > -- ---------------------------------------------------------------------------------------- MzK "Achieving happiness requires the right combination of Zen and Zin."
