Deutsch   English   Français   Italiano  
<lo7fpbFc70iU2@mid.individual.net>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder2.eternal-september.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: rbowman <bowman@montana.com>
Newsgroups: comp.os.linux.misc
Subject: Re: The joy of Ada
Date: 27 Oct 2024 18:40:43 GMT
Lines: 18
Message-ID: <lo7fpbFc70iU2@mid.individual.net>
References: <pan$96411$d204da43$cc34bb91$1fe98651@linux.rocks>
	<vf5442$sjo3$1@dont-email.me> <20241021075543.00000494@gmail.com>
	<vf6f0q$13ctc$2@dont-email.me> <20241021151652.00005675@gmail.com>
	<vf6n47$14l9a$3@dont-email.me> <lno9vqF368kU2@mid.individual.net>
	<vf6u3q$15nlq$3@dont-email.me> <20241022095931.00001d38@gmail.com>
	<vf93a5$1l20u$6@dont-email.me> <20241022144815.00007ea5@gmail.com>
	<vf98l2$1lsqn$3@dont-email.me> <20241022153631.00002ec9@gmail.com>
	<vfamtn$21039$1@dont-email.me> <vfbo4u$28v56$5@dont-email.me>
	<vfcft1$2ftu7$1@dont-email.me> <vfcgcv$2g0g1$3@dont-email.me>
	<nv2dnXjQd4-8foT6nZ2dnZfqn_sAAAAA@earthlink.com>
	<vfcptl$2hjp4$1@dont-email.me>
	<CCadnQ4B-oXSboT6nZ2dnZfqnPidnZ2d@earthlink.com>
	<vfebuf$2pkdl$4@dont-email.me>
	<Os6dnedZ6uqxbof6nZ2dnZfqn_WdnZ2d@earthlink.com>
	<nCQSO.297925$EEm7.62385@fx16.iad> <lo2as5Fj476U1@mid.individual.net>
	<qn_SO.297938$EEm7.187626@fx16.iad> <vfif3b$3m055$4@dont-email.me>
	<y7aTO.203218$WtV9.22893@fx10.iad> <vfl257$bic6$4@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net dGJz1tFnjg2Gu2x7CWaMXgaUzs+5c5nQBWwePGob2kYKhvnrfL
Cancel-Lock: sha1:J1p5dJCKmnQyTQ1Ei8qNUm55YXo= sha256:/3dUXTglAxY4oIV1H4CM2PtCCPndcF760V3HZpOXNa4=
User-Agent: Pan/0.149 (Bellevue; 4c157ba)
Bytes: 2745

On Sun, 27 Oct 2024 09:46:15 +0000, The Natural Philosopher wrote:

> I never bothered learning the more arcane side of SQL because if I ever
> managed to get the query right, it was always so abysmally slow that it
> was quicker to use a series of simple queries and join them together in
> application code rather than SQL

We had a support person who spent days if not months crafting a query 
using about every DB2 scalar function known to man. I forget the DB2 
versions but it started to fail on an older one that only allowed a 4k 
buffer but worked on the newer ones that handled 8k. Being a series of 
CONCATs if anything in the chain returned null the whole thing failed. 

It was a work of art that was copied from site to site unchanged because 
nobody, including myself, could figure it out. When we needed an 
equivalent for SQL Server which didn't have some of the matching scalars I 
took the programming approach. I use joins sparingly but there reaches a 
point where you're being too cute and it's unmaintainable.