It's no more then a roundtrip. However, each fetch is a roundtrip, which is
a design flaw of the current protocol.

On Wed, Oct 22, 2014 at 3:09 PM, Jacobson, Miranda <
mjacob...@volcanocorp.com> wrote:

>  Thank you for the response. I have a question about doing this.
>
>
>
> Is this a light weight operation? I ask because I would be twitching back
> and forth between Update and ReadOnly frequently and wanted to make sure
> there would be no impact on performance.
>
>
>
> Thank you,
>
>
>
> Miranda Jacobson
>
>
>
> *From:* Ivan Shcheklein [mailto:shchekl...@gmail.com]
> *Sent:* Thursday, October 16, 2014 2:06 AM
> *To:* Jacobson, Miranda; sedna-discussion
> *Subject:* Re: [Sedna-discussion] Read only access
>
>
>
> Hi Miranda,
>
>
>
> 1. After SEConnect
>
> 2. Yes, you can change it, whenever you like. Note, though, that the
> current transaction can be commited during this operation.
>
>
>
> Regards
>
> Ivan
>
> Sedna Team
>
>
>
> On Thu, Oct 16, 2014 at 2:26 AM, Jacobson, Miranda <
> mjacob...@volcanocorp.com> wrote:
>
> I have a question concerning the C API. There is a *SEsetConnectionAttr *that
> can be called with an attribute, *SEDNA_READONLY_TRANSACTION or
> SEDNA_UPDATE_TRANSACTION. *
>
> My question is does this have to be called before  SEconnect for it to
> take affect or can I keep changing this attribute during the entire
> connection?
>
>
>
> Thanks,
>
>
>
> Miranda Jacobson
>
>
>
> ----------------------------------------------------------------------------------
> NOTICE: The information contained in this electronic message and any
> attachments to this message may contain information that is privileged,
> confidential, or is otherwise protected by work product immunity. If the
> reader of this message is not the intended recipient, or an employee or
> agent responsible for delivering this message to the intended recipient,
> you are hereby notified that any dissemination, distribution, use, copying,
> and/or disclosure of its contents is strictly prohibited. If you have
> received this message in error, please notify us immediately by either
> replying to this message or calling Volcano Corporation at +1 (800)
> 228-4728 and, deleting this message from your computer.   ­­
>
>
>
> ------------------------------------------------------------------------------
> Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Sedna-discussion mailing list
> Sedna-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sedna-discussion
>
>
>
>
> ----------------------------------------------------------------------------------
> NOTICE: The information contained in this electronic message and any
> attachments to this message may contain information that is privileged,
> confidential, or is otherwise protected by work product immunity. If the
> reader of this message is not the intended recipient, or an employee or
> agent responsible for delivering this message to the intended recipient,
> you are hereby notified that any dissemination, distribution, use, copying,
> and/or disclosure of its contents is strictly prohibited. If you have
> received this message in error, please notify us immediately by either
> replying to this message or calling Volcano Corporation at +1 (800)
> 228-4728 and, deleting this message from your computer.   ­­
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Sedna-discussion mailing list
> Sedna-discussion@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sedna-discussion
>
>
------------------------------------------------------------------------------
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion

Reply via email to