
| Key: |
CORE-744
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
unruledboy
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
Firebird Core
Created: 11/Feb/05 12:00 AM
Updated: 14/Jun/06 09:42 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
SFID: 1120610#
Submitted By: unruledboy
object-featured RMDBS seems to be popular nowadays.
ever thinking of that?
|
|
Description
|
SFID: 1120610#
Submitted By: unruledboy
object-featured RMDBS seems to be popular nowadays.
ever thinking of that? |
Show » |
|
Sender: mapopa
Logged In: YES
user_id=85089
This freature should be closed
I will quote form CJ DATE interview
http://www.oreillynet.com/pub/a/network/2005/07/29/cjdate.html?page=2
Object/relational DBMSs: To a first approximation,
"object/relational" just means the domains over which
relations are defined can be of arbitrary complexity. As a
consequence, we can have attributes of relations--or columns
of tables, if you prefer--that contain geometric points, or
polygons, or X rays, or XML documents, or fingerprints, or
arrays, or lists, or relations, or any other kinds of values
you can think of. But this idea too was always part of the
relational model! The idea that the relational model could
handle only rather simple kinds of data (like numbers, and
strings, and dates, and times) is a huge misconception, and
always was. In fact, the term object/relational, as such, is
just a piece of marketing hype ... As far as I'm concerned,
an object/relational system done right would simply be a
relational system done right, nothing more and nothing less.