Primary Keys and ATK - Revision history

Bahati at 09:56, 11 March 2011

2011-03-11T09:56:32Z

← Older revision		Revision as of 09:56, 11 March 2011
Line 1:		Line 1:
	{{howto\|Easy\|[[Lorna Mitchell]] ~~<lorna@ibuildings.nl>~~}}		{{howto\|Easy\|[[Lorna Mitchell]]}}

	When first working with new software, it is sometimes helpful to look directly at the database, and sometimes we want to insert records manually to allow us to work with another part of the system before the data can be added in the usual way. When records are inserted manually to the database, then errors may appear in the ATK interface at a later stage, complaining about a duplicate key.		When first working with new software, it is sometimes helpful to look directly at the database, and sometimes we want to insert records manually to allow us to work with another part of the system before the data can be added in the usual way. When records are inserted manually to the database, then errors may appear in the ATK interface at a later stage, complaining about a duplicate key.

Lorna: Updating to reflect the AF_OBLIGATORY flag problem I had

2008-09-03T16:50:22Z

Updating to reflect the AF_OBLIGATORY flag problem I had

← Older revision		Revision as of 16:50, 3 September 2008
Line 13:		Line 13:
	== Using Automatically Incrementing Columns ==		== Using Automatically Incrementing Columns ==

	It is possible to work with automatically incrementing columns and ATK, but there are a few things that need to be changed. ~~Rather~~ than ~~using~~ the ~~AF_AUTOKEY for~~ the ~~primary key of a node~~, ~~the flag~~ AF_PRIMARY ~~should be used. You should also make sure that when~~ saving, ~~you send~~ a NULL value to allow the database to do its own id insertion, using a function like the one below (assuming your column is called "id"):		It is possible to work with automatically incrementing columns and ATK, but there are a few things that need to be changed. When adding the attribute, use the AF_PRIMARY flag rather than AF_AUTOKEY - it is also necessary to remove the AF_OBLIGATORY flag; the result looks something like this:

			<syntaxhighlight lang="php">
			$attr = &$this->add(new atkAttr("id",AF_PRIMARY\|AF_HIDE));
			$attr->removeFlag(AF_OBLIGATORY);
			</syntaxhighlight>

			When saving the record, a NULL value is sent to allow the database to do its own id insertion, using a function like the one below (assuming your column is called "id"):

	<code>		<code>

Lorna: fixing code layout

2008-07-09T15:55:04Z

fixing code layout

← Older revision		Revision as of 15:55, 9 July 2008
Line 1:		Line 1:
	{{howto\|Easy\|[[Lorna Mitchell]] <lorna@ibuildings.nl>}}		{{howto\|Easy\|[[Lorna Mitchell]] <lorna@ibuildings.nl>}}

	When first working with new software, it is sometimes helpful to look directly at the database, and sometimes we want to insert records manually to allow us to work with another part of the system before the data can be added in the usual way. When records are inserted manually to the database, then errors may appear in the ATK interface at a later stage, complaining about a duplicate key.		When first working with new software, it is sometimes helpful to look directly at the database, and sometimes we want to insert records manually to allow us to work with another part of the system before the data can be added in the usual way. When records are inserted manually to the database, then errors may appear in the ATK interface at a later stage, complaining about a duplicate key.
Line 16:		Line 16:

	<code>		<code>
	public function initial_values() {		public function initial_values() {
	return array("id"=>NULL);		return array("id"=>NULL);
	}		}
	</code>		</code>

	Take care though that if you use NF_EDITAFTERADD or any of the postEdit functionality, this will not work unless you specifically retrieve the value of the inserted record.		Take care though that if you use NF_EDITAFTERADD or any of the postEdit functionality, this will not work unless you specifically retrieve the value of the inserted record.

Lorna: Adding notes on primary keys that I gathered working on a recent ATK project

2008-07-09T15:54:27Z

Adding notes on primary keys that I gathered working on a recent ATK project

← Older revision		Revision as of 15:54, 9 July 2008
Line 1:		Line 1:
	{{howto\|Easy\|[[Lorna Mitchell]] <lorna@ibuildings.nl>}}		{{howto\|Easy\|[[Lorna Mitchell]] <lorna@ibuildings.nl>}}

			When first working with new software, it is sometimes helpful to look directly at the database, and sometimes we want to insert records manually to allow us to work with another part of the system before the data can be added in the usual way. When records are inserted manually to the database, then errors may appear in the ATK interface at a later stage, complaining about a duplicate key.

			Tables in ATK do not have auto_increment columns for their primary keys. This is a deliberate design decision to allow the system to be database-independent, since not all database platforms support the auto_increment. Instead the increments are handled as a sequence, with the sequence values stored in db_sequence.


			== Manually Inserting Data ==

			To manually insert data you should refer to the db_sequence table for the next id to use, then insert your data including the id into the table. If you want to insert multiple rows then go ahead and do this, with new id values for each row. Once you have finished inserting data, go back to the db_sequence table and update it with the next id to use so that ATK can continue to operate on this table.


			== Using Automatically Incrementing Columns ==

			It is possible to work with automatically incrementing columns and ATK, but there are a few things that need to be changed. Rather than using the AF_AUTOKEY for the primary key of a node, the flag AF_PRIMARY should be used. You should also make sure that when saving, you send a NULL value to allow the database to do its own id insertion, using a function like the one below (assuming your column is called "id"):

			<code>
			public function initial_values() {
			return array("id"=>NULL);
			}
			</code>

			Take care though that if you use NF_EDITAFTERADD or any of the postEdit functionality, this will not work unless you specifically retrieve the value of the inserted record.

Lorna: Creating the page

2008-07-09T15:03:38Z

Creating the page

New page