Re: [Firebird-docs] Consider migrating to GitHub?
On 19-12-2016 11:39, Andre van Zuydam wrote: > So bouncing in here on a tangent, I've done this with a couple of > Source forge projects, simply set Source forge to clone the Github > project or visa versa. The only reason I would suggest having things on > Github is for more visibility. Anyway my five cents. You can still > continue to commit as always, just have things cloned on both. Each > versioning system has its pros and cons, those of us who started with > CVS may have moved on to use other systems but hey, its such a mission > to switch things that work. That works (barely) if you already have a git project on SourceForge, but as far as I know not if you have CVS project on SourceForge. If a conversion is going to happen (but the strong resistance seems to indicate no), then I'd prefer going GitHub the way the core project did as well, instead of having a hybrid solution where you try to balance between GitHub and SourceForge and having to keep both repositories in-sync. Mark -- Mark Rotteveel -- Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/intel ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Clarification for MON$RECORD_STATS
Ah, makes things clearer. Thank you, Paul. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
Re: [Firebird-docs] Clarification for MON$RECORD_STATS
>From Helen's bible... 1. MON$RECORD_BACKOUTS Number of records where a new primary record version is backed out due to a rollback or savepoint undo 2. MON$RECORD_PURGES Number of records where the record version chain is being purged of versions no longer needed by OAT or younger transactions 3. MON$RECORD_EXPUNGES Number of records where record version chain is being deleted due to deletions by transactions older than the OAT Where OAT = Oldest Active Transaction. Paul -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
[Firebird-docs] Clarification for MON$RECORD_STATS
Hi, currently I translate the chapter about monitoring tables. I'm a bit confused in section MON$RECORD_STATS. Please show the differences of following columns: 1. MON$RECORD_BACKOUTS 2. MON$RECORD_PURGES 3. MON$RECORD_EXPUNGES I need more details here. Especially for MON$RECORD_PURGES and MON$RECORD_EXPUNGES. In German it means almost DELETE. But I think there is a huge difference to MON$RECORD_DELETES. Regards Martin -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot___ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
