(Edited to add: cross-posted! Great minds think alike.)
That's impressive, if people have scattered single quotes around variety names like:
This has bigger heads than 'Little Gem', but smaller than 'Forellenschluss'.
I guess you can limit "replace" operations to single fields, and those free-text-numeric-range fields ought not to have much chatty text in them.
>> But if you were going to do that simultaneous to other data points, then by all means, do.
No, I ran out of things to say about lettuce. I was thinking about mining 2015 seed catalogs for new varieties to add, but I like to have at least two sources before adding info to the database.
>> I thought engineers would be using the metric system.
The aviation world is very conservative. We measure speed in knots or feet per second ... because the Wright Brothers did it that way.
Units are always a pain. In one project, "tire pressure" was scaled or used different units THREE different ways, depending on which system the data was being sent to.
Sometimes "standardization" is five different people all screaming "do it MY way".
(I think one of the Arianne crashes was due to different units being used in different parts of the software, but someone forgot to convert. )
Also, "compatibility is everything". If those fields had been easily searchable , sticking to one system or the other would have been vital.
Also, I grew up with inches and can visualize those easier than cm. On the other hand, "3/64ths of an inch" means nothing to me, but I can visualize 5 mm.
>> Never, ever type "1 feet," Rick.
Never when speaking English, but I make no promises if I ever construct a database. Text comparisons can fail if one word has a SPACE after it, and another doesn't. Unless you use a TRIM function.
