In article <EpbYa.81520$o%2.37140@sccrnsc02>, davem405 (AT) comcast (DOT) net
says...
Not to burden you, but could you illustrate this statement with an
example? Thanks.

----------------------------------------
Paul Tiseo, Systems Programmer
Research Computing Facility, Mayo Clinic
tiseo128.paul23 (AT) mayo (DOT) edu
(please remove numbers to email me)

Hi,

FirstSQL/J provides integrated support for objects with internal O/R mapping
of Java types to database types. In FirstSQL/J, table columns can have an
object class as their datatype. The value of an object column can be an
instance of its defined class or one of its subclasses.

FirstSQL/J extends SQL to allow you to call the methods of object columns. A
simple
query example:

SELECT shape FROM shape_table WHERE shape.getHeight() < 14;

Object columns have data (fields in the object) *and* behavior (methods in
the object).
Extended object capabilities enhance the strengths of SQL.

For another example please see: http://www.firstsql.com/javaobjects.shtml

Cataloging Java classes as objects in the database is done with the CREATE
CLASS command;

CREATE CLASS object-name FROM 'java-name' [INHERITS class-list]
object-name is a string containing the fully qualified name of the Java
object being created. java-name is the name of the original base Java class
or a Java Interface being cataloged. In the optional INHERITS clause,
class-list is a comma-separated list containing the base Java class(s) (if
any) and any user-defined interfaces implemented. The base class or primary
interface is listed first. Any class or interface listed is cataloged in the
database with the database name used in the database class.

Hope this is clear enough.
Best regards,

Dave

"Paul Tiseo" <tiseo128.paul23 (AT) mayo (DOT) edu> wrote