Then, people can use the built-in features of Entity to view and CRUD the {async_command} table.

Comments

danithaca’s picture

Priority: Normal » Minor
Status: Active » Postponed

doesn't seem to be very critical

danithaca’s picture

Version: » 7.x-1.x-dev
Status: Postponed » Closed (won't fix)

Don't think this is necessary. Direct db table access is more flexible for development purpose anyway. The major advantage of make async_command a Drupal entity is that then it's easy to display it via Views. This is perhaps better to use Views API.