Reply to thread

Message

<blockquote data-quote="chefkoch" data-source="post: 1026674" data-attributes="member: 10438">Regarding the SQLite plugin, I would like to suggest the following:<ul>
<li data-xf-list-type="ul">commit the code (either to Incubator or Backend\Database &gt; morpheus can decide this) within it's own branch: SQLiteDatabase 
</li>
<li data-xf-list-type="ul">create a second branch (or within your own fork...) where this plugin is enabled and the MSSQLDatabase is disabled:&nbsp; SQLite_ENABLED</li>
</ul>The SQLite_ENABLED might contain only one commit for disabling and enabling the two DB plugins.This way you can rebase one commit as much as you want, without the need to rebase a lot of commits from the actual SQLite plugin and it's fixes etc. over and over. So the history of SQLiteDabase branch won't be broken.This way the SQLiteDatabase plugin also can be merged to dev earlier than it is rock-solid stable &amp; tested, because it is not enabled and won't actually effect the products' stability.</blockquote>

[QUOTE="chefkoch, post: 1026674, member: 10438"] Regarding the SQLite plugin, I would like to suggest the following: [LIST] [*]commit the code (either to Incubator or Backend\Database > morpheus can decide this) within it's own branch: SQLiteDatabase [*]create a second branch (or within your own fork...) where this plugin is enabled and the MSSQLDatabase is disabled: SQLite_ENABLED [/LIST] The SQLite_ENABLED might contain only one commit for disabling and enabling the two DB plugins. This way you can rebase [B]one[/B] commit as much as you want, without the need to rebase a lot of commits from the actual SQLite plugin and it's fixes etc. over and over. So the history of SQLiteDabase branch won't be broken. This way the SQLiteDatabase plugin also can be merged to dev earlier than it is rock-solid stable & tested, because it is not enabled and won't actually effect the products' stability. [/QUOTE]

Verification