When user right clicks on an event Outlook opens message
and request about 270 properties. GetProps is very slow in
this case. For a recurrent appointment Outlook also creates
an attachment(for store an exception if user selects 'this
occurence')
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2006-06-05
Logged In: YES
user_id=1456
Since message object is transacted fixing '[ 1499068 ] Use
memory database for transacted objects' should go a long way
in fixing this bug then.
There are issues surrounding attachments/tables and
transacted objects still.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When user right clicks on an event Outlook opens message
and request about 270 properties. GetProps is very slow in
this case. For a recurrent appointment Outlook also creates
an attachment(for store an exception if user selects 'this
occurence')
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When user right clicks on an event Outlook opens message
and request about 270 properties. GetProps is very slow in
this case. For a recurrent appointment Outlook also creates
an attachment(for store an exception if user selects 'this
occurence')
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
we can store current PropList in a hash table
so we can optimize searching non existing properties.
That should speed up _IntGetProps for a large prop set very
much. (even for in memory database)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1325778
When user right clicks on an event Outlook opens message
and request about 270 properties. GetProps is very slow in
this case. For a recurrent appointment Outlook also creates
an attachment(for store an exception if user selects 'this
occurence')
Logged In: YES
user_id=1456
Since message object is transacted fixing '[ 1499068 ] Use
memory database for transacted objects' should go a long way
in fixing this bug then.
There are issues surrounding attachments/tables and
transacted objects still.
Logged In: YES
user_id=1325778
When user right clicks on an event Outlook opens message
and request about 270 properties. GetProps is very slow in
this case. For a recurrent appointment Outlook also creates
an attachment(for store an exception if user selects 'this
occurence')
Logged In: YES
user_id=1325778
When user right clicks on an event Outlook opens message
and request about 270 properties. GetProps is very slow in
this case. For a recurrent appointment Outlook also creates
an attachment(for store an exception if user selects 'this
occurence')
Logged In: YES
user_id=1325778
we can store current PropList in a hash table
so we can optimize searching non existing properties.
That should speed up _IntGetProps for a large prop set very
much. (even for in memory database)