From 8c51fc9077bac0bd5b7a199b08fd3506a0cffcf6 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Mon, 6 Jul 2009 23:44:51 +0000 Subject: - Minor edits to tutorials for accuracy based on feedback. - Back to dev. --- docs/tutorials/bfgwiki2/definingmodels.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'docs/tutorials/bfgwiki2/definingmodels.rst') diff --git a/docs/tutorials/bfgwiki2/definingmodels.rst b/docs/tutorials/bfgwiki2/definingmodels.rst index 6f4809199..982865a80 100644 --- a/docs/tutorials/bfgwiki2/definingmodels.rst +++ b/docs/tutorials/bfgwiki2/definingmodels.rst @@ -30,16 +30,16 @@ code generated by our ``routesalchemy`` paster template does not use declarative SQLAlchemy syntax, so we'll need to change various things to begin to use declarative syntax. -Our ``Page`` class will have a class level attributes -``__tablename__`` which equals the string ``pages``. This means that -SQLAlchemy will store our wiki data in a SQL table named ``pages``. -Our Page class will also have class-level attributes named ``id``, -``pagename`` and ``data`` (all instances of ``sqlalchemy.Column``). -These will map to columns in the ``pages`` table. The ``id`` -attribute will be the primary key in the table. The ``name`` -attribute will be a text attribute, each value of which needs to be -unique within the column. The ``data`` attribute is a text attribute -that will hold the body of each page. +Our ``Page`` class will have a class level attribute ``__tablename__`` +which equals the string ``pages``. This means that SQLAlchemy will +store our wiki data in a SQL table named ``pages``. Our Page class +will also have class-level attributes named ``id``, ``pagename`` and +``data`` (all instances of ``sqlalchemy.Column``). These will map to +columns in the ``pages`` table. The ``id`` attribute will be the +primary key in the table. The ``name`` attribute will be a text +attribute, each value of which needs to be unique within the column. +The ``data`` attribute is a text attribute that will hold the body of +each page. We'll also remove our ``populate`` function. We'll inline the populate step into ``initialize_sql``, changing our ``initialize_sql`` -- cgit v1.2.3