Andrus Adamchik <andru..bjectstyle.org> wrote:
> However if you are fetching an object (say an Artist), all columns that
> map to the object attributes (plus PK and FKs) are fetched. Otherwise a
> valid object can't be created. So if you need an object, but don't need
> all attributes, here is another option - only map a subset of columns
> as ObjAttributes. In the Artist example, you can for example delete
> "dateOfBirth" attribute from the entity, so "DATE_OF_BIRTH" column will
> never be fetched.
You could also probably create two different ObjEntities for the same
database table. I'd probably mark one or both read-only.
In any case, you'd want to be sure that you never tried to update the same
table record at the same time.
-Mike
This archive was generated by hypermail 2.0.0 : Fri Oct 22 2004 - 13:10:39 EDT