Eric
Posts: 5743
Joined: 10/10/2003
From: Seattle, WA
Status: online
|
DATABASE HYGIENE
(1) I made a few changes in order to ensure consistency if the data in the database. Now if a user tries to insert a designation of "Premier Cru" they will always get "1er Cru" for the sake of consistency. When entering a vineyard or appellation, the database for checks to see if there is an existing match for the same string simply replacing spaces with dashes. So for example, if a user tries to enter "Puligny Montrachet" as an appellation or "Charmes Chambertin" as a vineyard, these will now match against the existing "Puligny-Montrachet" and "Charmes-Chambertin" strings instead of creating near dupes.
(2) For quite a long while now, the database has tried to avoid duplication of entries where only extended characters differ. So for example, if a user tries to enter "St. Estephe" as an appellation they will match against the existing "St. Estèphe" in the database. This has worked well to prevent dupes, but there was a subtle bug. If an existing dupe pair was in the database (for example, we had "Moet & Chandon" as well as "Moët & Chandon"), any attempt to add or edit a wine using this producer would result in an error. After fixing a few of these cases, I made some changes to prevent the error. I will still attempt to weed out any remaining near dupes, but now they are a lot less annoying.
FIT AND FINISH
The producer dropdown on the advanced query page now shows content with commas in place, just as the underlying sort is done. So for example, now "Château Angélus" appears in this dropdown as "Angélus, Château" to better support sane keyboard navigation.
_____________________________
Cheers!
-Eric LeVine
|
Printable Version
v 2.0.8 release notes - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread