On Sunday 23 December 2007 8:03 pm, johnf wrote: > > > The source is the bizobj; i.e., the 'DataSource'. The update() > > > method is called frequently; it would not be wise to have it > > > constantly requerying the database. > > > > I sort of understand. Let me see if I can work this out. In my case the > > bizobj refers to a table (which from the documentation is the 'default' > > use) so I saw the table as the DataSource, not the bizobj. What you are > > saying is that the bizobj as the middleware component caches data in its > > structure and update() works on that structure and requery() works on the > > underlying table. Am I getting close? > > Yes it sounds good to me! > > > If my assumptions above are correct I can see how this would be a > > problem. To play the Devils advocate I prefer that data is automatically > > saved when moving from record to record. I have greater faith in a > > database table holding data than an application. My inclination is to > > make the data hit the database soon and often. From poking around I can > > see ways to make that happen, I just have to work out the procedure. > > Not my cup of tea but as you have discovered Dabo is very flexible and > should beable to work for you. Don't forget you are working with Postgres > and you will have to consider changing the way transaction processing is > handled. I am not sure I follow. My experience with Psycopg is that is very fast and that doing small transactions is not an issue. -- Adrian Klaver [EMAIL PROTECTED]
_______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
