It seems that this module is actually providing support for functionality that is partially implemented by dba module. Although I try to see the basic motivation for TAPIr, I can rather see a direct benefit for dba module if this functionality was available in there. IMHO, combining dba and TAPIr modules results in a functionality that is similar to phpMyAdmin/pgAdmin.
Even if there is no thinkable way of merging those modules I'd like to propose to provide the basic functionality of adding/altering/deleting tables, adding/altering/deleting columns and adding/altering/deleting table rows in a separate API module (that still might be included in TAPIr), so that other modules like dba can rely on these functions.
Comments
Comment #1
rszrama commentedI'm not entirely sure what you're referring to here, but the dba module is for database tables whereas TAPIr is for outputting HTML tables to the screen. While TAPIr could be used to improve an interface for a database management module, I don't see any overlap between the modules.
What this module is for is filling a table with data from the database, not actually the database tables. A third party module could then add a column to the table for display based on other information stored in the database. An example from Ubercart is the product table on order view/edit screens. By default, it display the quantity, name, module number, and price for each product on an order. Another module included with Ubercart lets store owners define manufacturers for their products and adds manufacturer fields to these tables.
Let me know if anything here is unclear.
Comment #2
sunOk, seems like I didn't get the point of this module (even after visiting the demo).
Thank you for replying!
Comment #3
(not verified) commented