[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bash
From: |
Tim Visher |
Subject: |
Re: Bash |
Date: |
Wed, 15 Apr 2020 11:05:24 -0400 |
On Tue, Apr 14, 2020 at 4:54 PM Chet Ramey <address@hidden> wrote:
> On 4/14/20 4:33 PM, Tony Esposito wrote:
> > Thanks, I'll check it out. Just a quick question: Is anyone working
> on a
> > database interface for bash, like one usually finds in other scripting
> > languages such as Perl (e.g. Perl DBI)?
>
> Not that I know of. Is there widespread need or desire for one?
>
I've wanted it but I use bash for things that I shouldn't. :P
Database queries. When retrieving a tuple from a relational database, there
> is no way for Bash to understand where one element of the tuple ends and
> the next begins. In general, Bash is not suited to any sort of data
> retrieval that extracts multiple data values in a single operation, unless
> there is a clearly defined delimiter between fields. For database queries
> (SQL or otherwise), switch to a language that supports the database's query
> API.
- https://mywiki.wooledge.org/BashWeaknesses
- Bash, Tony Esposito, 2020/04/12
- Re: Bash, Jonesy, 2020/04/12
- Re: Bash, Chet Ramey, 2020/04/13
- Re: Bash, Tony Esposito, 2020/04/14
- Re: Bash, Chet Ramey, 2020/04/14
- Re: Bash,
Tim Visher <=
- Re: Bash, Jeffrey Walton, 2020/04/15
- Re: Bash, Chet Ramey, 2020/04/15
- Re: Bash, Jeffrey Walton, 2020/04/15
- Re: Bash, Greg Wooledge, 2020/04/15
- Re: Bash, Chet Ramey, 2020/04/15
- Re: Bash, Tim Visher, 2020/04/15
- Re: Bash, Greg Wooledge, 2020/04/15
- Re: Bash, Stephane Chazelas, 2020/04/19