Użytkownik John Fabiani napisał:
> I'm directing this off line as to not embarrass myself.
>
> I always read your posts with interest. But in this case could you explain a
> little more. I'm not sure what you mean by "interference" with respect to
> python or Dabo. It could be that my ignorance is showing. A google search of
> "Python interference" reveals nothing that makes sense here. I also checked
> "python inference" and discovered several entries. Yet I'm not sure how they
> apply.
>
For example, actual matter I'm working on.
I have a virtual filed which refers to PostgreSQL
large objects.
Ok, but how to write LO to the backend, since Dabo
doesn't support writeable virtual fields?
Solution seems to be simple, just overwrite dBizobj.setFieldVal().
Unfortunately it could be deceiving, because field accessing
methods in dBizobj works at this class level,
while dBizobj.Record refers directly to raw, cursor data row.
This is why dBizobj.setFieldVal("field", val) isn't the same
as dBizobj.Record.field = val.
I see that in Dabo examples, you use both access methods
interchangeably and in most cases they are, but it's not the same.
So, my only notice is, there should be a clear information
with dBizobj.Record property, it doesn't refer to business
layer by no means.
--
Regards
Jacek Kałucki
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message: http://leafe.com/archives/byMID/[email protected]
