You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Russ Trotter <ru...@yahoo.com> on 2001/12/07 22:00:27 UTC
Q: Torque, transactions and MySQL
Hello,
I'm trying get a feel for what kind of transactional support can be
accessed/enabled in Torque. I've gone through the setup to get a MySQL
instance to use the InnoDB table type so that transactional operations
can be used. The trick is, what's the best way to get the InnoDB table
type generated at the SQL generation phase?
I could make a patch that would plug a "TYPE=InnoDB" after every
"create table" at SQL generation time, but I have a feeling that people
may not want every table set for this type.
russ
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Torque, transactions and MySQL
Posted by Russ Trotter <ru...@yahoo.com>.
ok, so the misinformation is cleared up : ) I was referring to
Torque-standalone however. We're not
using Turbine in our app.
So, I take this time to reiterate, can anyone comment on whether it's
wise for me to make a patch that add 'type=InnoDB' to torque standalone?
russ
Scott Eade wrote:
>From: "Russ Trotter" <ru...@yahoo.com>
>
>>I just made some simple snippet of SQL that created an InnoDB table type
>>with a BLOB column and it worked with inserts at the mysql command
>>prompt.. Are you saying there are torque issues here or am I missing
>>something?
>>
>
>Sorry for the miss-information. I must have been recalling something from
>an old version. It appears that InnoDB does in fact support blobs.
>
>My comment concerning the DB security service still applies - changes
>to users, groups, etc using TurbineSecurity cannot be included in your
>transactions as DBSecurityService and DBUserManager do not cater
>for them.
>
>Cheers,
>
>Scott
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Torque, transactions and MySQL
Posted by Scott Eade <se...@backstagetech.com.au>.
From: "Russ Trotter" <ru...@yahoo.com>
> I just made some simple snippet of SQL that created an InnoDB table type
> with a BLOB column and it worked with inserts at the mysql command
> prompt.. Are you saying there are torque issues here or am I missing
> something?
Sorry for the miss-information. I must have been recalling something from
an old version. It appears that InnoDB does in fact support blobs.
My comment concerning the DB security service still applies - changes
to users, groups, etc using TurbineSecurity cannot be included in your
transactions as DBSecurityService and DBUserManager do not cater
for them.
Cheers,
Scott
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Torque, transactions and MySQL
Posted by Russ Trotter <ru...@yahoo.com>.
I just made some simple snippet of SQL that created an InnoDB table type
with a BLOB column and it worked with inserts at the mysql command
prompt.. Are you saying there are torque issues here or am I missing
something?
Scott Eade wrote:
>>
>
>I seem to recall that InnoDB tables don't support blobs. How would
>you handle the objectdata columns in the turbine security tables?
>
>I guess you could just leave them as the default table type since you
>can't include them in a transaction anyway - the default DB security
>service does not allow for them.
>
>Scott
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Torque, transactions and MySQL
Posted by Jon Stevens <jo...@latchkey.com>.
on 12/7/01 2:28 PM, "Scott Eade" <se...@backstagetech.com.au> wrote:
> I seem to recall that InnoDB tables don't support blobs. How would
> you handle the objectdata columns in the turbine security tables?
You could override that security stuff in Turbine and not use those columns.
They aren't really used anyway.
-jon
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Torque, transactions and MySQL
Posted by Scott Eade <se...@backstagetech.com.au>.
From: "Russ Trotter" <ru...@yahoo.com>
> I'm trying get a feel for what kind of transactional support can be
> accessed/enabled in Torque. I've gone through the setup to get a MySQL
> instance to use the InnoDB table type so that transactional operations
> can be used. The trick is, what's the best way to get the InnoDB table
> type generated at the SQL generation phase?
I seem to recall that InnoDB tables don't support blobs. How would
you handle the objectdata columns in the turbine security tables?
I guess you could just leave them as the default table type since you
can't include them in a transaction anyway - the default DB security
service does not allow for them.
Scott
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>