did someone use a object database?

[Diceman]

Is there a way I can unsee that photo?

 

[udg]

I wonder how the bathroom furniture can possibly fit his size..eheh

 

[LucaMs]

Oh, va bene, ho capito che conoscete la lingua tedesca, ma questo a noi interessa poco; anzi, niente

object.Save
object=object.Load(id)
no worry of stupid table structs

The "stupid tables" have to main purposes:

1) represent an "object"
2) allow you to perform searches, filtering and associations/relations (via non-stupid queries).

Saving a complex object, in binary format or xml/json text does not have the same usefulness.

 

[MarkusR]

Oh, va bene, ho capito che conoscete la lingua tedesca, ma questo a noi interessa poco; anzi, niente
The "stupid tables" have to main purposes:
1) represent an "object"
2) allow you to perform searches, filtering and associations/relations (via non-stupid queries).
Saving a complex object, in binary format or xml/json text does not have the same usefulness.

see
https://en.wikipedia.org/wiki/Database_normalization
a table represent some data of a "object" and split everything in tables with links between is terrible and then if you need all for a report u need long querys.

object databases can also have indexing and a search.
sql querys are text, uncheckable and raise run time erros. means if u rename a field in db, if u wrote names wrong in sql etc.

if u can save a whole class/object with all sub objects it have much usefulness. u not need a db table/field mapping. u not have a db struct.

 

[LucaMs]

So, if you had an object that represents a customer's purchase order for a product, you save this complete object, rather than having several tables (Customer, Order, Item,...).
By saving the whole object, you will have precisely what the normalization avoids: redundancy.

 

[MarkusR]

So, if you had an object that represents a customer's purchase order for a product, you save this complete object, rather than having several tables (Customer, Order, Item,...).
By saving the whole object, you will have precisely what the normalization avoids: redundancy.

i never saw a object database, i guess it save each object separately and each object have also an primary key.

-----------------------
https://en.wikipedia.org/wiki/Object_database
https://en.wikipedia.org/wiki/Comparison_of_object_database_management_systems