Creat View in the SQL and than use it in the SQLObject as an ordinary table.
You can handle some more complex SQL SELECT within the view.
Of course it is read only (I am on Firebird - maybe some other databases
behave differently)
HTH
Petr
On 1 July 2010 20:38, Mark <markree...@gmail.com> wrote:
>
> > +1VIEW is, IMHO, en excelent way to go, when the SQLObject is close to
> its
> > limits.Petr
>
> How do you create and use a view in SQLObject?
>
> And is not a view a tradeoff on response time vs DB size? If I create a
> separate
> table with a million rows I may add 50mb to the DB size, but if I use a
> view the
> DB has to select out the view each time and that 50mb may not cache.
>
> Mark
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> sqlobject-discuss mailing list
> sqlobject-discuss@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
