|
> From: Joe Pluta > > And I still disagree. While the data may be the user's, the database is > MINE and always will be. And lest this get mis-interpreted, this is not a territorial issue, it's a job definition issue. It's not the user's job to ensure data integrity. It's not the user's job to ensure fail-over capability. It's not the user's job to ensure transaction completion. It's not the user's job to ensure data availability. No, those are MY jobs as the programmer. And to that end, it's in both of our best interests that there remains a clear delineation between the concept of "data" (or more correctly "information") and concept of the database. Information is what the user should be able to get, wherever and whenever they need it. The database, on the other hand, is the place where this information is stored. I hate analogies, because they're almost by definition inaccurate, but let me give one that at least makes snese to me. Your valuables are yours, and you should be able to access them whenever you need to. But if you store them in a safety deposit box in my bank, you have to go through my procedures to get at them. If not, I cannot ensure their safety. And that is my final opinion on that subject. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.