From: Victor B. <vb...@gm...> - 2014-01-20 17:14:16
|
On Mon, Jan 20, 2014 at 3:27 AM, Paul Richards <pa...@ma...> wrote: > My comment: As soon as 1.3 is out the door, I'll be putting in a pull > request to replace the db api with the layer we started on for > next/mantis2. I'll spend 3 hours a day testing and developing that support > and ensuring a good experience on all database engines to get that pull > request into a state that enables me to run the latest master of mantis > against mssql directly, as opposed to the mess that currently exists. > [Victor] I would recommend doing this on a branch, testing it there, and we merge it when two things happen. 1.3.0 stable is released (hence hopefully less merging) and that the new db layer is provide to be solid. What I'm trying to avoid is to introduce a merging pain right away. > Personally, I'm happy with just supporting MySQL for now (as > postgresql/mssql are known to be broken), and then fixing it properly > moving forwards from 1.4. > [Victor] +1. That is the plan. > What I'm less keen on is making changes and saying we support mssql for > instance, then when we look at it properly in 1.4 finding out that the > database types (or whatever) generated by adodb are incorrect (we've had > that before) and that we end up with messing users around again. > [Victor] We can work on the messaging. My priority is not to block 1.3 on this. I know Damien had an opinion about this. Thanks, -Victor |