--- In firebird-support@yahoogroups.com, "Steve Miller" <Steve_Miller@
...> wrote:

>
>
> We have a guy that has been doing research on an alternate

approach.

> He's storing the object data in an XML string. The XML string is

stored

> in the only field of a table. The table is the only one in the

system.

> He's reporting huge performance increases with this approach.
>

There should be no performance increases, I would expect performance
decrease more likely.

> Have any of you heard of anything like this? What do you see are

the

> pros and cons of such an approach?

Pros:
Good if you can have only one table in dabatase.
Storing object with complex hierarchy when details of hierarchy is
not important.
Storing object changes history for all classes in model.
At least object key should be added as second database field :-).

Cons:
referential integrity
query system - have to abandon SQL and invent your own
before doing anything you must load ALL objects into memory
slow



Regards,
Zlatko Ivankovic