-Developing data models in OpenACS 4 is much like developing data models
+Developing data models in OpenACS 4.5 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
@@ -64,12 +64,12 @@
Allow other applications to use notes in ways we don't know of yet.
-In OpenACS 4, the key to enabling these types of services on your
+In OpenACS 4.5, the key to enabling these types of services on your
application data is to take advantage of the Object System. The first
question anyone asks is usually "Just what are objects, and what do
you use them for anyway?". The short answer: objects are anything
represented in the application's data model that will need to be
-managed by any central service in OpenACS 4, or that may be reusable in
+managed by any central service in OpenACS 4.5, or that may be reusable in
the context of future applications. Every object in the system is
represented using a row in the acs_objects table. This
table defines all the standard attributes that are stored on every
@@ -110,7 +110,7 @@
new object type. Object types are analogous to classes in
programming languages such as C++ and Java. For example, in Java a
class defines a set of attributes that store data and a set of methods
-that run code. In OpenACS 4, we use one or more Oracle tables to store the
+that run code. In OpenACS 4.5, we use one or more Oracle tables to store the
data attributes, and we define a PL/SQL package to hold procedures to
define the programming interface to the data model.
@@ -128,11 +128,11 @@
Fire up your text editor and open the
ROOT/packages/notes/sql/notes-create.sql file created
-during the earlier created the package. Then, do the following:
+during the earlier 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:
@@ -202,7 +202,7 @@
-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
@@ -234,7 +234,7 @@
-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
@@ -268,7 +268,7 @@
You might be wondering what all the extra parameters are to these
calls, since we haven't mentioned them before. These parameters are
needed to fill out information that will be stored about the object
-that's not stored directly in the table you defined. The OpenACS 4 Object
+that's not stored directly in the table you defined. The OpenACS 4.5 Object
System defines these attributes on the type acs_object
since all objects should have these attributes. Internally, there are
tables that store this information for you. Most of the data is pretty
@@ -290,7 +290,7 @@
-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
@@ -412,7 +412,7 @@
system.
-There are two basic rules you should follow when designing OpenACS 4 data
+There are two basic rules you should follow when designing OpenACS 4.5 data
models:
@@ -480,7 +480,7 @@
Summary
-Hooking into the OpenACS 4 object system brings the application developer
+Hooking into the OpenACS 4.5 object system brings the application developer
numerous benefits, and doing it involves only four easy steps:
@@ -519,21 +519,21 @@