From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c9d5fc258548b22a
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news3.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!nx02.iad01.newshosting.com!209.197.12.242.MISMATCH!nx01.iad01.newshosting.com!newshosting.com!198.186.194.249.MISMATCH!transit3.readnews.com!news-out.readnews.com!postnews7.readnews.com!not-for-mail
Date: Fri, 04 Mar 2011 11:48:06 -0500
From: Hyman Rosen <hyrosen@mail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.9.2.14) Gecko/20110221 Thunderbird/3.1.8
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: How do I write directly to a memory address?
References: 
 <67063a5b-f588-45ea-bf22-ca4ba0196ee6@l11g2000yqb.googlegroups.com>
 <05a3673e-fb97-449c-94ed-1139eb085c32@x1g2000yqb.googlegroups.com>
 <4d4c232a$0$28967$882e7ee2@usenet-news.net> <4D4D6506.50909@obry.net>
 <4d50095f$0$22393$882e7ee2@usenet-news.net>
 <wcck4hb95jz.fsf@shell01.TheWorld.com>
 <4d6d56c4$0$11509$882e7ee2@usenet-news.net>
 <16u9ka51wbukr$.1fj2sb73j9rv6.dlg@40tude.net>
 <4d6d627b$0$11509$882e7ee2@usenet-news.net>
 <74986d0a-0d5b-4396-8c77-adff72e870a2@d26g2000prn.googlegroups.com>
 <4d6eafc7$0$17913$a8266bb1@postbox2.readnews.com>
 <op.vrqh3z1blzeukk@jellix.jlfencey.com>
 <4d6eb309$0$17913$a8266bb1@postbox2.readnews.com>
 <op.vrqodiwglzeukk@jellix.jlfencey.com>
 <4d6ed212$0$17960$a8266bb1@postbox2.readnews.com>
 <8985b302-96b8-4f22-aa4d-d64945047f90@r4g2000prm.googlegroups.com>
 <4d6ee8e2$0$14912$882e7ee2@usenet-news.net> <ikn0a7$7g0$1@munin.nbi.dk>
 <4d6f2fcb$0$14547$882e7ee2@usenet-news.net> <ikpbcs$ko1$1@munin.nbi.dk>
In-Reply-To: <ikpbcs$ko1$1@munin.nbi.dk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <4d7117da$0$27719$882e7ee2@usenet-news.net>
NNTP-Posting-Host: d33a2707.usenet-news.net
X-Trace: 
 DXC=9X^7`CF:BAhXXUSNMl8T[dQFZ3T]GPM]gmX0AG3X_jUoiS_LH4mLFmfVjKk:Lk^BNacR12TN^Bg7nh\Gmfl9l;^mYL0D@=LTG4h
X-Complaints-To: abuse@usenet-news.net
Xref: g2news1.google.com comp.lang.ada:17816
Date: 2011-03-04T11:48:06-05:00
List-Id: <comp.lang.ada>

On 3/3/2011 7:22 PM, Randy Brukardt wrote:
> Which is the best (and virtually only) reason for using them, IMHO.
 > If you don't need wild scaling, you probably don't need a database.

I have found in practice that it is much more useful to have data
stored in a database instead of in a custom persistence mechanism.
The main reason is that as part of my job, I frequently have to
search the data in various ad hoc ways. It is easy to do this with
a database; I write some SQL and retrieve the data instantly, or
if the query is too slow, I can get an appropriate index added and
then retrieve the data instantly. When I have to deal with the
custom persisters, I find that the only way to retrieve data is by
writing programs to invoke their custom methods, and then they
support queries only in the way they have envisioned that the data
would be needed, so that it takes more programming work to do what
I need.