torque and views (read-only tables)

["Diethelm Guallar, Gonzalo" <Go...@sonda.com>]

I'm thinking of improving support for Views in torque.
Right now I just define a bunch of tables for my views,
and the Peers work just fine, except that they have all
the methods to insert/update/delete. My question is, would
it be good enough to be able to do

  <table name="foo" readOnly="yes">

or would you rather use

  <view name="foo">

which is a little more work to implement?


-- 
Gonzalo A. Diethelm
gonzalo.diethelm@sonda.com

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org

Re: torque and views (read-only tables)

[Daniel Rall <dl...@collab.net>]

"Diethelm Guallar, Gonzalo" <Go...@sonda.com> writes:

> I'm thinking of improving support for Views in torque.
> Right now I just define a bunch of tables for my views,
> and the Peers work just fine, except that they have all
> the methods to insert/update/delete. My question is, would
> it be good enough to be able to do
> 
>   <table name="foo" readOnly="yes">
> 
> or would you rather use
> 
>   <view name="foo">
> 
> which is a little more work to implement?

Don't overload table to support views.  Having a view directive makes
more sense, but an exception should be thrown if the database that SQL
is being generated for doesn't support views.

Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org