Index: openacs-4/packages/acs-core-docs/www/objects.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.adp,v diff -u -r1.1.2.2 -r1.1.2.3 --- openacs-4/packages/acs-core-docs/www/objects.adp 23 Sep 2015 18:37:45 -0000 1.1.2.2 +++ openacs-4/packages/acs-core-docs/www/objects.adp 28 Sep 2015 07:54:21 -0000 1.1.2.3 @@ -83,7 +83,7 @@ for the PG version) file created when we created the package. Then, do the following:
First, add an entry to the acs_object_types
table with the following
PL/SQL call:
begin @@ -139,7 +139,7 @@ attributes, so there is no need for us to define them.
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 note
, but also an acs_object
. The new table definition looks
@@ -163,7 +163,7 @@
acs_objects
.
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:
@@ -210,7 +210,7 @@ We'll talk about this more later.
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
@@ -361,8 +361,8 @@
acs_objects
. This means you
should never use the fields in acs_objects
for application-specific
purposes. This is especially true for the context_id
field.