Can we have a discussion about how to remove the gross and disgusting
hack in the postgres driver regarding binary objects? Hacking the
postgres driver in this fashion is clearly not the right thing to do.
There seem to be several possible "correct" solutions....
Either the Village API needs to stop assuming that a field can only be
accessed in one fashion, either integer or binary, and the decision
needs to be made elsewhere about whether to look at it as binary or
integer.
or
Stop using large objects to solve this problem. Large objects are a
pretty awful thing anyway, even more so in postgres where they are
horribly inefficient.
At first glance, I would say do both. Village can't go through life
making
this assumption that you can't pull binary data out of a particular
field type. And I don't feel at all good running a postgres installation
with large objects because I know how awful the implementation is (think
1 or 2 files for every object!)
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
