cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Ball <>
Subject database actions
Date Thu, 08 Mar 2001 21:19:33 GMT
heya. just testing berin's database actions out - good stuff! let me make
sure i'm following the flow control properly - when a request for
/forms/employee received, c2 checks to see if there's a request parameter
named cocoon-action. if so, it fires off the proper action. in any case,
it'll render the edit employee(s) form. correct so far?

the database manipulation actions rely on a form-descriptor parameter
which gives some meta-information about the table(s) in question, e.g.:

<?xml version="1.0"?>

  <table name="employee_table">
      <key param="employee" dbcol="id" type="int" mode="manual"/>
      <value param="name" dbcol="name" type="string"/>
      <value param="department" dbcol="department_id" type="int"/>


what's the benefit of grouping the actions together into an action set?

- donald

To unsubscribe, e-mail:
For additional commands, email:

View raw message