Re: Doing better at HINTing an appropriate column within errorMissingColumn()
От | Alvaro Herrera |
---|---|
Тема | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
Дата | |
Msg-id | 20140709211946.GR6390@eldon.alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Doing better at HINTing an appropriate column within errorMissingColumn() (Peter Geoghegan <pg@heroku.com>) |
Ответы |
Re: Doing better at HINTing an appropriate column within errorMissingColumn()
|
Список | pgsql-hackers |
Peter Geoghegan wrote: > On Wed, Jul 9, 2014 at 8:08 AM, Greg Stark <stark@mit.edu> wrote: > > A simple rule is easier for users to understand as well as to code. I > > would humbly suggest the following: take all the unqualified column > > names, downcase them, check which ones match most closely the > > unmatched column. Show the top 3 matches if they're within some > > arbitrary distance. > > That's harder than it sounds. You need even more translatable strings > for variant ereports(). Maybe it is possible to rephrase the message so that the translatable part doesn't need to concern with how many suggestions there are. For instance something like "perhaps you meant a name from the following list: foo, bar, baz". Couple with the errmsg_plural stuff, you then don't need to worry too much about providing different strings for 1, 2, N suggestions. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: