← Back to team overview

mvhub-dev team mailing list archive

Re: New sqlite / postgresql specific problems

 

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>
> 
> 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;


Follow ups