Restriction + temporary changes possible?

MyNickname

just two questions before buying - what would be the best/eastiest way
- to implement a layer for access/restriction (create, remove, update, delete; on column or row level for user)?
- to load data from table and save the changes in a tempoary table (e.g., table user + change something + save = save into t_user) ... so it is not directly saved into a productive database and someone can review the changes?

tnx

allan

• to implement a layer for access/restriction (create, remove, update, delete; on column or row level for user)?

The security section in the Editor manual has some degree of information about this. It focuses mainly on column level, but you could use a global validator for row level.

• to load data from table and save the changes in a tempoary table (e.g., table user + change something + save = save into t_user) ... so it is not directly saved into a productive database and someone can review the changes?

Its an interesting one this, as you need to consider what to do when the user reloads the page. Does it just show the original unedited data, in which case "where have my changes gone" will be their first reaction? Or does it need to try and join the two tables together for that user? That's the approach I would take myself, but it isn't something that Editor's provided server-side libraries handle at the moment. That said, to implement this you'd check to see if the request is to get the data or create/edit/delete data and if so, change the target table name based on that.

Another option is to have an audit table, information for which can be found here

Allan