Sujet : Re: Serial, concurrent, parallel
De : invalid (at) *nospam* invalid.invalid (Edward Rawde)
Groupes : sci.electronics.designDate : 17. Jan 2025, 05:22:48
Autres entêtes
Organisation : BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID : <vmcluq$2drc$1@nnrp.usenet.blueworldhosting.com>
References : 1 2 3 4 5 6 7 8
User-Agent : Microsoft Outlook Express 6.00.2900.5931
"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.
>
Date | Sujet | # | | Auteur |
14 Jan 25 | Serial, concurrent, parallel | 35 | | Don Y |
14 Jan 25 |  Re: Serial, concurrent, parallel | 9 | | Liz Tuddenham |
14 Jan 25 |   Re: Serial, concurrent, parallel | 8 | | Don Y |
14 Jan 25 |    Re: Serial, concurrent, parallel | 7 | | Liz Tuddenham |
15 Jan 25 |     Re: Serial, concurrent, parallel | 6 | | Don Y |
16 Jan 25 |      Re: Serial, concurrent, parallel | 5 | | Liz Tuddenham |
16 Jan 25 |       Re: Serial, concurrent, parallel | 4 | | Don Y |
16 Jan 25 |        Re: Serial, concurrent, parallel | 3 | | Liz Tuddenham |
16 Jan 25 |         Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |         Re: Serial, concurrent, parallel | 1 | | ehsjr |
16 Jan 25 |  Re: Serial, concurrent, parallel | 20 | | Martin Brown |
16 Jan 25 |   Re: Serial, concurrent, parallel | 19 | | Don Y |
16 Jan 25 |    Re: Serial, concurrent, parallel | 16 | | Liz Tuddenham |
16 Jan 25 |     Re: Serial, concurrent, parallel | 13 | | Don Y |
16 Jan 25 |      Re: Serial, concurrent, parallel | 12 | | Liz Tuddenham |
16 Jan 25 |       Re: Serial, concurrent, parallel | 5 | | Don Y |
17 Jan 25 |        Re: Serial, concurrent, parallel | 4 | | Liz Tuddenham |
17 Jan 25 |         Re: Serial, concurrent, parallel | 3 | | Don Y |
17 Jan 25 |          Re: Serial, concurrent, parallel | 1 | | Don Y |
17 Jan 25 |          Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |       Re: Serial, concurrent, parallel | 6 | | Edward Rawde |
17 Jan 25 |        Re: Serial, concurrent, parallel | 5 | | Don Y |
17 Jan 25 |         Re: Serial, concurrent, parallel | 4 | | Edward Rawde |
17 Jan 25 |          Re: Serial, concurrent, parallel | 3 | | Don Y |
17 Jan 25 |           Re: Serial, concurrent, parallel | 2 | | Edward Rawde |
17 Jan 25 |            Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |     Re: Serial, concurrent, parallel | 2 | | Martin Brown |
16 Jan 25 |      Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |    Re: Serial, concurrent, parallel | 2 | | Martin Brown |
16 Jan 25 |     Re: Serial, concurrent, parallel | 1 | | Don Y |
16 Jan 25 |  Re: Serial, concurrent, parallel | 5 | | brian |
16 Jan 25 |   Re: Serial, concurrent, parallel | 3 | | john larkin |
17 Jan 25 |    Re: Serial, concurrent, parallel | 2 | | brian |
17 Jan 25 |     Re: Serial, concurrent, parallel | 1 | | john larkin |
16 Jan 25 |   Re: Serial, concurrent, parallel | 1 | | Don Y |