well, I can work on it. Basically the issue is how are we going to resolve it ? Is it acceptable that the sqlform.grid search widget always works only with dates in ISO format (i.e. it will disregard whatever regional setting is otherwise chosen)? If yes, I have more or less yet an idea on how to fix it. If instead we want the search widget to use the same "localized" format for the date, and let the grid handle out the "re-translation" to something not local, then it will require more work.
On Tuesday, August 20, 2013 4:21:24 PM UTC+2, LightDot wrote: > > This is of some interest to me too. Issue > 1640<http://code.google.com/p/web2py/issues/detail?id=1640>created. > > On Sunday, August 18, 2013 9:58:28 AM UTC+2, Massimo Di Pierro wrote: >> >> Good point. The search is performed in the database format which is ISO >> (Y/m/d). The grid is not smart enough to apply local settings (custom data >> formats) to the search field. You may want to open a ticket about this and >> we'll see what we can do. >> >> On Saturday, 17 August 2013 12:43:23 UTC-5, Leonardo Pires Felix wrote: >>> >>> I've found something, when i do the search using the date picker, it >>> returns me in the format of the translation file("%d/%m/%Y"), but when use >>> like this to do the search, it returns nothing or something not expected. >>> But if i mannually change the format from the search on the sqlform.grid to >>> "%Y/%m/%d" it works out. How do to the sqlform.grid recognize the format >>> that i want to use on the search("%d/%m/%Y") ? >>> >>> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
