Members   Search   FAQ    Register    Login   Home

Show: Today's Messages  :: Show Polls :: Message Navigator

[SQLITE] Primary keys are never defined as AUTOINCREMENT [message #67245] Wed, 10 December 2008 02:32  Riccardo Messages: 26 Registered: December 2008 Location: Trento, Italy Junior Member If you are using SQLite, you should be aware that primary key ID values of deleted records can get reused for newly-inserted records, unless you specify the AUTOINCREMENT keyword in the column definition. This is explained in more detail on this page of the SQLite site. Propel 1.3, which Symfony uses to translate your schema.yml file into SQL statements, will never use the AUTOINCREMENT keyword in a SQLite database, even if you explicitly specify so. This is an issue with Propel rather than with Symfony itself; nonetheless I thought it might be useful to report it here, in case someone ever uses the blessed Search link. Report message to a moderator

	[SQLITE] Primary keys are never defined as AUTOINCREMENT  By: Riccardo on Wed, 10 December 2008 02:32
	Quick and dirty workaround By: Riccardo on Wed, 10 December 2008 10:47
	Re: [SQLITE] Primary keys are never defined as AUTOINCREMENT By: xplo on Wed, 10 December 2008 22:21
	Re: [SQLITE] Primary keys are never defined as AUTOINCREMENT By: Riccardo on Thu, 11 December 2008 00:31

Previous Topic:	symfony 1.2 - Defect in forms framework or not?
Next Topic:	[Solved] build-model messing up mysql's longtext

Goto Forum: