Re: SCB1381 - Scarab summary page

Hi @ all,

I hope you all had a nice easter weekend.

But now to the report problem: The problem was not the user instance, 
but the caching. In a multi user environment every user has its own 
instance of the module. So all caching trials will fail.

Cheers

Völker Ronny schrieb:
> Hi Johannes,
>
> if I understand it right, the Report, as well as the ReportBridge are independent of the user.
> So there has to be just one ReportBridge-Object referencing the defeault-Report for each ScarabModule.
> That's why there should be no problem at all with multiple users and multiple sessions.
>
> How about a Method:
>    Module.getDefaultReportBridge()
> or ReportManager.getDefaultReportBridge( module )
> or a static Report.getDefaultReportBridge( module )
> which returns a (cached) ReportBridge-Object for the default Report of a module.
> In this case you need just the module, if you want to invalidate cached report-data.
>
> Ronny
>
> -----Original Message-----
> From: Johannes Hoechstaedter [mailto:[email protected]] 
> Sent: Monday, March 10, 2008 1:41 PM
> To: [email protected]
> Subject: Re: SCB1381 - Scarab summary page
>
> ok :) here ist is, thank you
>
> Völker Ronny schrieb:
>   
>> Hello Johannes,
>>
>> I think there should be a solution without an additional column.
>> Could you please post a patch with your current changes?
>> I will have a look at it.
>>
>> Ronny
>>
>>
>> -----Original Message-----
>> From: Johannes Hoechstaedter [mailto:[email protected]]
>> Sent: Monday, March 10, 2008 1:19 PM
>> To: [email protected]
>> Subject: Re: SCB1381 - Scarab summary page
>>
>> Hi guys
>>
>> I am tired in struggeling with the multi user ability of the default 
>> report patch. Now I have the probelm, that a report is set to dirty 
>> only for one user (because of the instance) I want to set the report 
>> dirty fo all. Therefore I want to introduce a column in the database 
>> with a dirty flag. Do you have any other ideas or is it ok?
>>
>> cheers
>> Johannes
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected] For 
>> additional commands, e-mail: [email protected]
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected] For 
>> additional commands, e-mail: [email protected]
>>
>>
>>
>>   
>>     
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
>
>