Hello!
I'm working on a modification of the engine which bypasses the
obligatory data conversion via field lists and profiles. The use case
for this are client and server which perfectly agree on some proprietary
item data and thus need no conversion, or plugins which want to handle
the data
On Fri, 2010-05-14 at 10:46 +0100, Beat Forster wrote:
Hello Patrick
I'm working on a modification of the engine which bypasses the
obligatory data conversion via field lists and profiles. The use
case
for this are client and server which perfectly agree on some
proprietary
item
Hi Patrick
After reading the documentation of ContextSupport() it becomes a bit
clearer, but not much. Where is the complete list of support rules
that the plugin might have to handle?
There is currently only this rule supported by the engine. Originally
we thought there would be much
Hello Patrick,
I think by far the simplest method would be NOT to try to bypass
MultifieldItem, but derive it with an implementation that puts/gets data (and
maybe metadata) into/from well-known string or BLOB fields.
The entire DB API thing was developed long after we more or less settled for
On Fri, 2010-05-14 at 17:28 +0100, Lukas Zeller wrote:
Hello Patrick,
I think by far the simplest method would be NOT to try to bypass
MultifieldItem, but derive it with an implementation that puts/gets
data (and maybe metadata) into/from well-known string or BLOB fields.
The entire DB
Hello Patrick,
On May 14, 2010, at 19:56 , Patrick Ohly wrote:
On Fri, 2010-05-14 at 17:28 +0100, Lukas Zeller wrote:
Hello Patrick,
I think by far the simplest method would be NOT to try to bypass
MultifieldItem, but derive it with an implementation that puts/gets
data (and maybe
