On 3/2/2010 8:45 PM, Andreas Saeger wrote: > Fernand Vanrie wrote: >> Andreas , >> >> Your proposal is maybe a bit to drastic, but OO can, indeed, been a >> ideal frontend for any DB, included a Oracle Base :-), I hope they >> reed this dispared crys and gives us some exctra developer power. >> > > Yes, reduce Base to a better frontend. That was Base is already. > Drop that embedded caricature of a database backend. It's not a caricature. If it was one, then use MiniSQL or the like instead.
> It is slow, unsafe (too many reports about data loss), insecure (no > permissions) because behaves like an extension. It installs itself > before you can use it and it gets repackaged when you "close the > document". May be it was the most efficient way to accomplish what the > crowd shouted for (back in 2005) and certainly it was a nice toy for > educational purposes but now let it rest in peace. For single-user installations it is more than enough. Besides it has been improving over time. > If all the other pieces would work more consistently (simpler rather > than easier!) it could be a big improvement with less software to > maintain. > Just leave the job to create a relational database up to the > professionals and power users with their own tools for the respective > database backend. There is no need for a table designer or relation > editor in a mere frontend tool. False. As a matter of fact I know of sites which used MS Access for exactly those purposes (and not using the MSA's JetEngine). Even if there is some frustration, keep it in proportion (and let those gazillion single-users still have their database with Base). In addition, it may be possible that developers from the community step up/in? ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
