# Defining Models

The first change we'll make to our stock paster-generated application will be to define a :term:model constructor representing a wiki page. We'll do this inside our models.py file.

The source code for this tutorial stage can be browsed at docs.repoze.org.

## Making Edits to models.py

Note

There is nothing automagically special about the filename models.py. A project may have many models throughout its codebase in arbitrarily-named files. Files implementing models often have model in their filenames (or they may live in a Python subpackage of your application package named models) , but this is only by convention.

The first thing we want to do is remove the stock Model class from the generated models.py file. The Model class is only a sample and we're not going to use it.

Then, we'll add a Page class. Because this is a SQLAlchemy application, this class should inherit from an instance of :class:sqlalchemy.ext.declarative.declarative_base. Declarative SQLAlchemy models are easier to use than directly-mapped ones. The 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 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 :class: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 function to add a FrontPage object to our database at startup time. We're also going to use slightly different binding syntax. It will will otherwise largely be the same as the initialize_sql in the paster-generated models.py.

Our DBSession assignment stays the same as the original generated models.py.

## Looking at the Result of Our Edits to models.py

The result of all of our edits to models.py will end up looking something like this:

## Viewing the Application in a Browser

We can't. At this point, our system is in a "non-runnable" state; we'll need to change view-related files in the next chapter to be able to start the application successfully. If you try to start the application, you'll wind up with a Python traceback on your console that ends with this exception:

ImportError: cannot import name Model

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.