Attention

This document was written for an old version of Plone, Plone 3, and was last updated 1205 days ago.

To learn how to upgrade to the current version of Plone, read the upgrade manual.

Creating SQL content types with collective.tin

collective.tin is a library for creating RDBMS backed content types on top of SQLAlchemy. collective.lead is used for transaction integration. collective.mercury supports the autogeneration of interfaces, model and db files by introspecting the RDBMS schema. This approach does not require zodb stubs. Versioning is optional. Workflow status and history (if required) are stored in the database. (This tutorial is very much a work in progress, but I figured it may be useful to make it public now)

  1. Overview Over this tutorial we will develop a timesheet system to demonstrate the various features of collective.tin.
  2. Creating the database (1) Database creation and a users table
  3. Creating the content types (1) Building a product and using collective.mercury

All content on one page (useful for printing, presentation mode etc.)

 

Contribute

Something wrong or out of date? Anybody can edit or create a new article in the knowledge base. Simply create an account on this site, log in, and click the Edit button to contribute.