How about I move the Crud section to the end of the chapter, change the section heading to "CRUD (Deprecated)", and add the following note at the top of the section:
Note: Although the CRUD system described in this section will remain available for backward compatibility, it is no longer recommended. Its functionality has largely been subsumed by the newer SQLFORM.process() and SQLFORM.grid(), which are now the recommended methods for implementing CRUD functionality. I could also send a patch removing Crud() from db.py in the welcome app, and replace the /default/data function with one based on SQLFORM.grid(). Thoughts? Anthony On Tuesday, July 24, 2012 7:47:42 AM UTC-4, Massimo Di Pierro wrote: > > I think we should but I am afraid people may misunderstand. Crud is not > going away (because of backward compatibility), simply it is no longer the > recommended way to implement the functionality. > > On Monday, 23 July 2012 23:16:18 UTC-5, Anthony wrote: >> >> Should we mark Crud as deprecated in the book? >> >> On Monday, July 23, 2012 11:55:14 PM UTC-4, Massimo Di Pierro wrote: >>> >>> Please do not use crud. It is not needed any more. You can do everything >>> and better with SQLFORM().process(). >>> We are not going to change the behavior of curd now that we have a more >>> powerful tool (SQLFORM). >>> >>> On Monday, 23 July 2012 16:55:49 UTC-5, Najtsirk wrote: >>>> >>>> Hi, >>>> >>>> each time i want to update crud, i have to submit changes twice to get >>>> it actually updated. >>>> >>>> I set crud.settings.detect_record_change = False, which helps with >>>> 'text' fields, but the problem presists with 'boolean'. Boolean field get >>>> changed each time i update form, even though I do not change it. >>>> >>>> I'm getting this on 1.99.4 and on 1.99.7. >>>> >>>> I'm seeing this for the first time, but then again....i'm doing Blog >>>> app for the first time and there is a little more updating than in my >>>> other >>>> apps. >>>> >>>> Any clues? >>>> >>>> Best, >>>> Kristjan >>>> >>>> >>>> --
