Hi, (Sorry for slow replies, I am quite behind on my e-mails.) :-(
Sorry if this is a dumb or already hashed out question, but I seem to remember reading in the SQLObject documentation that you can use lazy updating. You just tell you model (I think) to do lazy updates, and then it's up to you to call the sync() method. http://sqlobject.org/SQLObject.html#lazy-updates Do people not know this, or is there some reason why that functionality, as it exists, is not sufficient? I just never see anyone talk about this particular implementation. Thanks, Krys Kevin Dangoor wrote: > On 11/1/05, modmans2ndcoming <[EMAIL PROTECTED]> wrote: > >>I am new to DB dev work, and I was just curious about Lazy updates. >> >>It seems that a lot of people are concerned about the number to updates >>that are generated using SQLObject. > > > I'm not sure about *a lot* of people... but there are certainly some. > > >>Lazy updates allow you to not update the db every time you make a >>change? Why is that important? How often do you change data after you >>update it? > > > Here's an example: > > foo.bar = "Hello" > > results in some SQL like: > > UPDATE Foo SET bar = 'Hello' where id=5 > > That gets sent on to your database server. > > Some people are concerned about the amount of traffic to the database > server if you end up not committing those changes. > > Kevin >
