Re: Confused on Where to Put SQL

2006-08-25 Thread Andy Todd
On 8/25/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > > On 8/24/06, bradford <[EMAIL PROTECTED]> wrote: > > > > it's actually going to be thousands of sql queries for each user. > > would doing it all in one object lock out all of the users for the > > entire time the "magic" is being done (until

Re: Confused on Where to Put SQL

2006-08-24 Thread Jeremy Dunck
On 8/24/06, bradford <[EMAIL PROTECTED]> wrote: > > it's actually going to be thousands of sql queries for each user. > would doing it all in one object lock out all of the users for the > entire time the "magic" is being done (until it is updated)? That depends on your database's transaction iso

Re: Confused on Where to Put SQL

2006-08-24 Thread bradford
it's actually going to be thousands of sql queries for each user. would doing it all in one object lock out all of the users for the entire time the "magic" is being done (until it is updated)? [EMAIL PROTECTED] wrote: > Do you really need to perform hundreds of SQL queries? Wouldn't it be > a l

Re: Confused on Where to Put SQL

2006-08-24 Thread Laundro
Do you really need to perform hundreds of SQL queries? Wouldn't it be a lot easier to load all of the data you need into an object, perform your magic on it and then write it all back to the database? --~--~-~--~~~---~--~~ You received this message because you ar

Confused on Where to Put SQL

2006-08-23 Thread bradford
It seems like I'm constantly using custom SQL statements, because the ORM won't offer what's necessary to achieve the desired data query/manipulation. Right now I need to wrap up the following in a transaction that will be called a few hundred times in a for loop. delete from table ... create te