mvhub-dev team mailing list archive

[Emaad Ahmed Manzoor <emaadmanzoor@xxxxxxxxx>]

Hi Dan and Ferhat,

10.10 Maverick - 3.7.2

So dependency: sqlite (>= 3.6.22) should be fine?

On Fri, Aug 5, 2011 at 2:47 AM, Ferhat Elmas <felmas@xxxxxxxxxx> wrote:

> **
> Hi,
> I have found this:
>
> 10.4   Lucid    -  3.6.22
> 11.4   Natty    - 3.7.3
> 11.10 Oneiric - 3.7.3
>
> Version 3.7.7.1 of SQLite is recommended for all new development.
> Upgrading from version 3.7.6.3 or 3.7.7 is optional. Upgrading from all
> other SQLite versions is recommended.
>
> 04.08.2011 18:04, Dan MacNeil yazmış:
>
> On 08/04/2011 04:02 AM, Ferhat Elmas wrote:
>
>   sqlite in brave is 3.5.9 and it has no foreign key support but we need
> 'em so we need to upgrade to 3.6.19 at least. (Current 3.7.7.1)
> ( the library must be compiled with neither SQLITE_OMIT_FOREIGN_KEY or
> SQLITE_OMIT_TRIGGER and foreign keys must still be enabled by the
> application at run time, using PRAGMA foreign_keys=ON; commmand)
> SQLITE Foreign Support <http://www.sqlite.org/foreignkeys.html> <http://www.sqlite.org/foreignkeys.html>
>
> Moreover, while submitting category data into database, again some
> postgre specific queries are used such as
> NEXTVAL_X_SEQUENCE
> SELECT nextval(?)
> for category_id_sequence
>
>  CC'ing the list as this is of interest at least to Jeff ( db stuff) and
> Emmad ( upgrading brave / staging / development )
>
>
> Tuesday night, I spent 5 hours getting part way toward migrating brave
> from Debian Lenny (5.x) to Debain Squeeze. (there are a lot of packages)
> I should finish today (at the cost of delaying code review)
>
> If a kind soul wanted to check to see what sqllite was provided with
> ubuntu 10.4  11.4 & 11.10 that would make deciding what to move the
> workstations to / what versions of ubuntu we were going to support
>
> Emmand, if your packaging scripts ( pre-inst ?) checked the sqlite
> version or declared a dependency on a specific version , that might be a
> good idea.
>
> Jeff,
>
> A quick stab at the problem might be to modify:
>
> 	MVHub::Utils::DB::get_next_in_sequence()
>
> ... so it:
>
> 	did a SELECT on a table
> 	incremented the value
> 	did an update on the table.
>
> You'd then have to add a .sql file to
> 	app-mvhub/setup/database/sql/
>
> ...to:
> 	start transaction;
> 	get the next value in each sequence
> 	drop the sequence
> 	create a replacement table
> 	add a row with the next sequence value
> 	commit;
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mvhub-dev
> Post to     : mvhub-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mvhub-dev
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mvhub-dev
> Post to     : mvhub-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mvhub-dev
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Emaad Ahmed Manzoor