-Developing data models in OpenACS 5.5.0 is much like developing data models
+Developing data models in OpenACS 5.6.0 is much like developing data models
for OpenACS 3, save for the implementation. As usual, you need to examine
how to model the information that the application must store and
manipulate, and define a suitable set of SQL tables. In our Notes
@@ -79,7 +79,7 @@
Fire up your text editor and open the
ROOT/packages/notes/sql/oracle/notes-create.sql (ROOT/packages/notes/sql/postgresql/notes-create.sql for the PG version) file created
when we created the package. Then, do the following:
-
Describe the new type to the type system
+
Describe the new type to the type system
First, add an entry to the acs_object_types table with the following PL/SQL call:
begin
@@ -139,7 +139,7 @@
because the new type note is a subtype of
acs_object, it will inherit these attributes, so there is
no need for us to define them.
-
Define a table in which to store your objects
+
Define a table in which to store your objects
The next thing we do is make a small modification to the data model to
reflect the fact that each row in the notes table
represents something that is not only an object of type
@@ -164,7 +164,7 @@
use the acs_objects table to find objects will
transparently find any objects that are instances of any subtype of
acs_objects.
-
Define a package for type specific procedures
+
Define a package for type specific procedures
The next step is to define a PL/SQL package for your new type, and
write some basic procedures to create and delete objects. Here is a
package definition for our new type:
@@ -212,7 +212,7 @@
object OBJ was "read only", then any other object that used OBJ as its
context would also be "read only" by default. We'll talk about this more
later.
-
Define a package body for type specific procedures
+
Define a package body for type specific procedures
The PL/SQL package body contains the implementations of the procedures
defined above. The only subtle thing going on here is that we must use
acs_object.new to insert a row into
@@ -315,7 +315,7 @@
models that are meant to be integrated with the OpenACS object
system.
-There are two basic rules you should follow when designing OpenACS 5.5.0 data
+There are two basic rules you should follow when designing OpenACS 5.6.0 data
models:
@@ -370,7 +370,7 @@
requires a good amount of thought at design time even for simple
applications.
-Hooking into the OpenACS 5.5.0 object system brings the application developer
+Hooking into the OpenACS 5.6.0 object system brings the application developer
numerous benefits, and doing it involves only four easy steps: