Feature Requests item #3490323, was opened at 2012-02-21 14:38 Message generated for change (Comment added) made by shcheklein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713733&aid=3490323&group_id=129076
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Export/Import >Group: None Status: Open >Priority: 3 Private: No Submitted By: Michael Woytowitz (zazz-coder) >Assigned to: Ivan Shcheklein (shcheklein) Summary: Export will lock ability to update Initial Comment: During the execution of se_exp export on a database one can not update any records. The database is completely locked until the export completes. I would prefer that this process NOT lock the database and allow updates but those updates will not be in the export based on the transaction date. ---------------------------------------------------------------------- >Comment By: Ivan Shcheklein (shcheklein) Date: 2012-03-26 03:38 Message: // Moved to feature request. It's not a bug. Yes. We have se_hb for non-blocking hot backup. Still, we can probably add option to se_exp to run in RO mode. ---------------------------------------------------------------------- Comment By: al-indigo (al-indigo) Date: 2012-02-21 15:01 Message: I may be wrong (Ivan, Ilya -- watch for this) but I was quete sure that we have a special utility for this: se_hb. Am I wrong? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=713733&aid=3490323&group_id=129076 ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Sedna-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sedna-discussion
