Packages/DigiComp.Sequence
2
0
Fork 0
Code Pull requests Releases Activity
No description
53 commits 6 branches 16 tags 147 KiB
PHP 100%
Find a file
Christian Krause 27b3bd9af1 TASK: Apply migration DigiComp.SettingValidator-20170603120900 
Restructures Validation.yamls to new format

Note: This migration did not produce any changes, so the commit simply
marks the migration as applied. This makes sure it will not be applied
again.
2018-04-03 13:50:46 +02:00
Classes just some code and annotation cleanup 2018-04-03 10:23:53 +02:00
Configuration/Testing update project; fit neos/flow 4 2017-03-13 16:59:04 +01:00
Migrations/Mysql update project; fit neos/flow 4 2017-03-13 16:59:04 +01:00
Tests/Functional update project; fit neos/flow 4 2017-03-13 16:59:04 +01:00
.gitignore Initial commit 2014-04-07 15:25:16 +02:00
composer.json TASK: Apply migration DigiComp.SettingValidator-20170603120900 2018-04-03 13:50:46 +02:00
License.txt TASK: Preparing first public release 2016-06-24 20:57:06 +02:00
README.md TASK: Moving Readme.md to README.md 2016-06-24 20:59:47 +02:00

README.md

DigiComp.Sequence

This is a very simple and stupid tool, helping in generation of gapless sequences. For this task it relies on key integrity of the database of your choice.

Usage is quite simple also:

/**
 * @param \DigiComp\Sequence\Service\SequenceNumberGenerator $sequenceNumberGenerator
 */
public function __construct(SequenceNumberGenerator $sequenceNumberGenerator) 
{
	$this->orderId = $sequenceNumberGenerator->getNextNumberFor($this);		
}

getNextNumberFor allows you to give an object which will be resolved to its FQCN or a custom sequence name.

The CommandController helps you to advance the current sequence number, in case of migrations or similar.

See ./flow help sequence:advance if interested.