![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
| I understand that PostgreSQL has OO capabilities. Is it possible to store full-blown Perl objects in a PostgreSQL table? (I suppose that one can always serialize Perl objects and store the serialized text, but this is hardly OO.) Thanks, kynn ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org |
#3
| |||
| |||
|
|
I understand that PostgreSQL has OO capabilities. |
|
Is it possible to store full-blown Perl objects in a PostgreSQL table? (I suppose that one can always serialize Perl objects and store the serialized text, but this is hardly OO.) |
#4
| |||
| |||
|
|
Kynn, I understand that PostgreSQL has OO capabilities. Nope! Bzzzzzzzz. Thank you for playing. ;-) We are Object-Relational, not Object Oriented. Object-Relational has to do with our custom data types, operators, aggregates, and table inheritance. It is not OO, or even really analogous. Is it possible to store full-blown Perl objects in a PostgreSQL table? (I suppose that one can always serialize Perl objects and store the serialized text, but this is hardly OO.) I suggest using Alzabo. Look it up on Freshmeat. -- Josh Berkus Aglio Database Solutions San Francisco ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
![]() |
| Thread Tools | |
| Display Modes | |
| |