On Thu, Jul 01, 2010 at 08:52:38PM +0200, Petr Jake?? wrote:
> 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.
+1
> Of course it is read only (I am on Firebird - maybe some other databases
> behave dif
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 wrote:
>
> > +1VIEW is, I
> +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 v
+1
VIEW is, IMHO, en excelent way to go, when the SQLObject is close to its
limits.
Petr
On 1 July 2010 18:28, Oleg Broytman wrote:
> On Thu, Jul 01, 2010 at 03:48:38PM +, Mark wrote:
> > Even if you weren't using SQLObject I believe it would make more
> > sense to create a separate name/i
On Thu, Jul 01, 2010 at 03:48:38PM +, Mark wrote:
> Even if you weren't using SQLObject I believe it would make more
> sense to create a separate name/id table and then only select
> from the 40 column table when you know what row you want.
Or use a VIEW.
Oleg.
--
Oleg Broytman
Even if you weren't using SQLObject I believe it would make more
sense to create a separate name/id table and then only select
from the 40 column table when you know what row you want.
Mark
--
This SF.net email is sp
On Tue, Jun 22, 2010 at 12:09:22PM +0200, Imre Horvath wrote:
> Thank you, that's what I've looking for.
> In my case, I only fill details view for one record only, 30-40 columns,
> it's fast enough with one-column queries too.
Oops, I've forgotten - lazyColumns by itself prevents loading of co
Thank you, that's what I've looking for.
In my case, I only fill details view for one record only, 30-40 columns,
it's fast enough with one-column queries too.
But I wonder if it's possible to override get method to temporary switch
off lazyColumns?
I mean:
class Customer(SQLObject):
def g
On Tue, Jun 22, 2010 at 11:20:39AM +0200, Imre Horvath wrote:
> Is it possible to select only a few columns from a table?
No, but you can lazily selects columns using lazyColumns=True; with this
SQLObject doesn't initially draw any column, only id's; but when you touch a
row and ask for a colum
Hi everyone!
Is it possible to select only a few columns from a table?
My primary problem is speed when i select all rows from a big table (>1
mill. record).
But i only need 2-3 columns from it. I think it's because all other
columns & related objects are selected.
FYI: The exact scenario is:
Cus
10 matches
Mail list logo
