Path: ...!news.misty.com!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: "Edward Rawde" <invalid@invalid.invalid>
Newsgroups: sci.electronics.design
Subject: Re: Serial, concurrent, parallel
Date: Thu, 16 Jan 2025 23:22:48 -0500
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Lines: 27
Message-ID: <vmcluq$2drc$1@nnrp.usenet.blueworldhosting.com>
References: <vm69a2$2h52d$1@dont-email.me> <vmam6l$3et7s$1@dont-email.me> <vmar9r$3g1ud$2@dont-email.me> <1r695ej.t31qiz7lhsjkN%liz@poppyrecords.invalid.invalid> <vmb2ko$3hal6$1@dont-email.me> <1r69dpn.1bbzdc81ozzc9wN%liz@poppyrecords.invalid.invalid> <vmbh9o$14pn$1@nnrp.usenet.blueworldhosting.com> <vmc36h$3mt5f$1@dont-email.me>
Injection-Date: Fri, 17 Jan 2025 04:22:50 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="79724"; mail-complaints-to="usenet@blueworldhosting.com"
Cancel-Lock: sha1:SKqKhOicBFV1Hybv+kYhSEOwE2Y= sha256:pDGxHHKNijjMo03GstP8qCj6c7NhiQ1Qu6BtTqoJ9pc=
	sha1:EeKEaESCngEeHfZ4UHJnPEIhZMs= sha256:uBKuiNPFDL/JsyUHyPSvHnXjKBOn0ETJRjSwPs1GMfc=
X-Priority: 3
X-RFC2646: Format=Flowed; Response
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Bytes: 2615

"Don Y" <blockedofcourse@foo.invalid> wrote in message news:vmc36h$3mt5f$1@dont-email.me...
> On 1/16/2025 10:57 AM, Edward Rawde wrote:
>> Databases can also be backed up as human readable text files.
>
> To be fair, a spreadsheet's contents can similarly be exported (CSV).
> I'm not sure how the formulae, formats, etc. are handled, though.
> And, any non-text entries (that might be supported).

In other words exporting a database as SQL is not in any way similar to exporting a spreadsheet as csv.
You might be better off unzipping the xlsx and parsing the xml if you really want your spreadsheet elsewhere.

>
>> Just export data as SQL.
>> This gives me peace of mind that whatever software is or isn't available in the future I can always read my data.
>
> The value of SQL as a "dump" format is that you can *import* it into
> another SQL DBMS -- as long as the recipient supports the same (or
> greater) level of features.  And, the import process is nothing more than
> piping the dump file to the recipient DBMS's "console" as it consists
> entirely of SQL commands.

I frequently paste an entire SQL dump into the Query tab in HeidiSQL.

>
>