On 6/22/01 8:11 AM, "Gunnar R�nning" <[EMAIL PROTECTED]> wrote:
> * Daniel Rall <[EMAIL PROTECTED]> wrote:
> |
> | Mike Haberman <[EMAIL PROTECTED]> writes:
> |
> | > Could you for now remap (db.props) blob to be of type integer ?
> | > Turbine doesn't need to use blob anywhere, so everything should
> | > work fine.
> |
> | -1 for inclusion of such a change into CVS. Fix the root of the
> | problem, not the symptoms. =)
> |
>
> The root of the problem is that BLOBs are not as portable as we would like
> them to be...
>
> I just tried this change, and it doesn't work for the default user admin app
> shipped with the tdk.
Yes, we know.
> Which version of Village is in use ? Is anybody looking into fixing this
> problem ?
Yes, I've been looking at it but I haven't figured out the whole problem
yet. It is a problem with large object support and the way the peers/village
deals with them. The use of large objects requires transactions and some
modification to the SQL used. That's about all I know so far.
> Also why is the postgresql jdbc driver shipped with the TDK. FYI the pgsql 7.1
> driver is not backwards compatible, since system table layout was changed
> in PostgreSQL 7.1. And there is a JDBC1 driver and JDBC2 driver for every
> release of postgresql.
It's included because it has a patch for blob support. Maybe we can
pick one as the recommended choice and include it. I'm in the process
of setting up a dual PIII machine that will be used to test turbine
against as many databases as I can get my hands on. I will figure
this out at some point.
> regards,
> Gunnar
--
jvz.
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
