M
Martin Brown
Guest
On 04/04/2023 06:30, Don Y wrote:
Not so much typeless as can be of any valid data type.
The peculiar thing here is that for reasons best known to itself Excel
DEC2HEX fails at 2^39 exactly). IOW
=DEC2HEX(2^39-1) works ok and shows 7FFFFFFFFF
=DEC2HEX(2^39) fails #NUM!
This is very odd when the standard float type can exactly represent any
power of two up to 2^(512+53) and the mantissa of a 64 bit FP can
exactly represent all numbers up to 2^54 (there is a hidden in the
hardware implicit leading 1 in all non-zero 64 bit FP values).
My pet hate on websites is having to put in a credit card number without
the spaces which makes it much easier to have an undetected typo. Groups
of four numbers separated by a space are trivial to flash read.
It isn\'t like removing spaces from a string is rocket science!
My other pet hate is collecting UK train tickets where in addition to
putting the card that you used to buy the train tickets you also have to
enter a high entropy code of 24 characters which does its best to
include one of all the ambiguos ones 1,I,l,0,O,5,S etc.
The delays this causes as people fight the stupid robotic ticket
dispenser to get their tickets is crazy! Now you can at finally download
them to a phone and avoid this queuing mess.
I have seen way too many spreadsheets used as databases causing chaos.
It starts out OK with a smallish prototype project and the grows like
topsy until one day no-one knows how it works or how to maintain it.
Upto a couple of thousand records it doesn\'t make much difference either
way but go much beyond that and it is \"here be dragons\" territory.
+1
Spreadsheets are easier for accounting and management types to
understand though - DBMS has a much steeper learning curve.
I rely on being able to remember what the cover looks like or now with
google and wiki having so much online some key phrase I can recall.
--
Martin Brown
On 4/3/2023 2:30 PM, Carlos E.R. wrote:
Not in a spreadsheet. Unless you treat the spreadsheet as a text table
and all of the data as typeless.
Not so much typeless as can be of any valid data type.
And, it\'s commonplace to have a DBMS put constraints on data
in ways that spreadsheets can\'t/don\'t. As well as having a wider
range of data types (how do you store a MAC in a spreadsheet?)
Infinite ways. As text, for example. As a huge number.
The reason you want \"typed\" fields is to reduce errors.
Is this a number: THIS
Is this a MAC:Â Â HeLlOboysandgirls
Is this a float:Â 123.456.78,,90
A MAC is just a long hexadecimal number that is displayed differently.
I\'m sure it can be done if the sheet software can handle hex. Mine
doesn\'t.
It not only has to be a *valid* 48 bit hex value but it can\'t be
anything *more* (or less) than those 12 hex digits.
The peculiar thing here is that for reasons best known to itself Excel
DEC2HEX fails at 2^39 exactly). IOW
=DEC2HEX(2^39-1) works ok and shows 7FFFFFFFFF
=DEC2HEX(2^39) fails #NUM!
This is very odd when the standard float type can exactly represent any
power of two up to 2^(512+53) and the mantissa of a 64 bit FP can
exactly represent all numbers up to 2^54 (there is a hidden in the
hardware implicit leading 1 in all non-zero 64 bit FP values).
Additionally, depending on the table in which it resides, it might
need to be different from all other MACs present in that field
(for other entries) -- because no two devices have the same MAC.
My pet hate on websites is having to put in a credit card number without
the spaces which makes it much easier to have an undetected typo. Groups
of four numbers separated by a space are trivial to flash read.
It isn\'t like removing spaces from a string is rocket science!
My other pet hate is collecting UK train tickets where in addition to
putting the card that you used to buy the train tickets you also have to
enter a high entropy code of 24 characters which does its best to
include one of all the ambiguos ones 1,I,l,0,O,5,S etc.
The delays this causes as people fight the stupid robotic ticket
dispenser to get their tickets is crazy! Now you can at finally download
them to a phone and avoid this queuing mess.
This is trivial to guarantee with a DBMS. With a spreadsheet
(or untyped text), you rely entirely on the discipline of the person
entering the data (and we all know people are notorious for making
mistakes!)
I have seen way too many spreadsheets used as databases causing chaos.
It starts out OK with a smallish prototype project and the grows like
topsy until one day no-one knows how it works or how to maintain it.
Upto a couple of thousand records it doesn\'t make much difference either
way but go much beyond that and it is \"here be dragons\" territory.
DBMSs present so many richer ways of presenting and preserving
data to make the DBAs job easier.
+1
Spreadsheets are easier for accounting and management types to
understand though - DBMS has a much steeper learning curve.
This is doubly so for technical articles.
[Coffee table books are handled entirely differently... they are
*intended* to be physical items that folks can peruse leisurely]
I rely on being able to remember what the cover looks like or now with
google and wiki having so much online some key phrase I can recall.
--
Martin Brown