| Deutsch English Français Italiano |
|
<vmed40$6qm7$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Don Y <blockedofcourse@foo.invalid> Newsgroups: sci.electronics.design Subject: Re: Serial, concurrent, parallel Date: Fri, 17 Jan 2025 13:04:06 -0700 Organization: A noiseless patient Spider Lines: 29 Message-ID: <vmed40$6qm7$1@dont-email.me> 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> <vmcluq$2drc$1@nnrp.usenet.blueworldhosting.com> <vmctge$3u72f$1@dont-email.me> <vmdhsl$30jh$1@nnrp.usenet.blueworldhosting.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 17 Jan 2025 21:04:17 +0100 (CET) Injection-Info: dont-email.me; posting-host="68adfa8e3e76f0eebe2e8c9bdf898e65"; logging-data="223943"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/iawc15PXxpPwpMNQohMrJ" User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Cancel-Lock: sha1:XtvVF+Aogx2viOXqLrrx7tVuDEQ= In-Reply-To: <vmdhsl$30jh$1@nnrp.usenet.blueworldhosting.com> Content-Language: en-US Bytes: 2970 On 1/17/2025 5:19 AM, Edward Rawde wrote: > "Don Y" <blockedofcourse@foo.invalid> wrote in message news:vmctge$3u72f$1@dont-email.me... >> On 1/16/2025 9:22 PM, Edward Rawde wrote: >>> "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. >> >> Of course it is. The difference lies in WHAT you are exporting. >> What does a 3MB photo (stored as a BLOB) look like when exported in SQL? >> Is it any more recognizable in that form? > > You may as well ask what it looks like when a jpg is opened in a text editor. You touted the fact that YOU can see your data as human readable files (in the event <something> happens to the database software). That this is an asset that DBMSs have over spreadsheets. My point is that this only partially works as you expect. A spreadsheet's contents can be exported as <whatever>-delimited form which will make the same sorts of data that are readable when exported in an SQL dump "readable", readable.