*** bigbrother` has joined #gnuenterprise
<jamest> test
<jamest> btami: iirc it takes some many lines before bigbrother will dump to log
<jamest> s/some/so
<jamest> so i'll type a bit
<jamest> reinhard: i need a few minutes before i can read your questions and reply
<reinhard> jamest: no problem
<reinhard> FWIW, logs are back as far as I can see
*** ajmitch has quit IRC
*** ajmitch has joined #gnuenterprise
<jamest> i guess we're still using bigbrother on the old ash computer
<jamest> reinhard: a lot of this could have changed over the years
<jamest> but i thought the datasource kept a single resultset
<jamest> that the blocks provided a view into
<jamest> that was independent of the datasource
<jamest> but the datasource didn't forget the resultset as it was responsible for noteing new,dirty, or deleted records and taking appropriate action
<jamest> but it's been years and at least 2 major overhauls of the data access system
<reinhard> that's why I'm asking
<jamest> so for all I know magic bunnies now track all that and push all the data through the NSA for proper archival
<reinhard> rofl
<reinhard> seriously
<reinhard> I've been asking to get the original concepts, not to find out how it works *now*
<jamest> well
*** johannesV has joined #gnuenterprise
<jamest> don't datasources now have the concept of nextRecord and prevRecord?
<jamest> and an iterator
<johannesV> oh, looks like i'm finished with upgrading from breezy to dapper ...
<johannesV> looks nice
<jamest> johannesV: it is nice
<jamest> for a KDE user anyway :)
<reinhard> jamest: no, datasources don't have next/prev record
<reinhard> only block and resultset have
<jamest> ok, i was thinking at one time the datasource added some of that functionality
<jamest> and that if a delete was in the datasource trigger namespace it was for use in those iterators
<jamest> i believe in the cases where i've needed to do that i iterate thru a block
<jamest> and use a block level delete function
<reinhard> you could also get yourself the resultset object, iterate through that (which gives you the RecordSet objects) and then call delete() of the RecordSet
<reinhard> it is still the case that datasource keeps track of the current result set
<reinhard> and I was curious if that is compatible with the concept of datasources because they could also be understood as "factories" for resultsets
<reinhard> because if all blocks bound to the same datasource share the same resultset, I don't see any use of having different blocks at all (because they will be in sync all the time anyway)
<reinhard> so datasource:block would always be 1:1 more or less
<reinhard> except for the cases where a datasource is used without block
*** btami has quit IRC
<reinhard> bbl
<johannesV> hm, the troubles with svn are still there
*** derek has joined #gnuenterprise
<jamest> sigh
<jamest> fwiw, there is a screensaver in debian's xscreensavers package called "Web Collage"
<jamest> it pulls random pics from the internet and adds one every few seconds to the display
<jamest> in case anyone here isn't aware of the fact there is a lot of porn on the internet
<jamest> and so today I get a call from a worker asking why i have a pornographic screensaver installed on our systems
<reinhard> lol
*** johannesV has quit IRC
*** klasstek has quit IRC
*** jamest has left #gnuenterprise
<reinhard> good night all
*** reinhard has quit IRC
*** llp has quit IRC
*** bigbrother_ has joined #gnuenterprise
*** bigbrother` has quit IRC
*** llp has joined #gnuenterprise
*** jcater has joined #gnuenterprise
*** bigbrother` has joined #gnuenterprise
*** bigbrother_ has quit IRC
*** jcater has left #gnuenterprise
*** llp has quit IRC