View source | Discuss this page | Page history | Printable version   

ERP 2.50:QA test plan 2.50/UUID



Currently in Openbravo ERP, database records are identified by one (in some tables it's two) numeric column which is known as primary key (PK). The value of a primary key cannot be repeated within the same table, or in other words once a primary key is taken it can't be used again in the same table while the record that identifies it is still in the table. Before any insertion in a database a PK is requested and reserved. This PKs are sequential numbers: for each request the reserved number is the next to the last reserved one for the table where it is going to be used. Additionally for each table two ranges of primary keys are maintained: one is for the system entries and another one for the common data entries. System entries are the ones that can be used by the system (they define application dictionary data and information shared among all the users).

As system information is intended to be shared between different installations the PKs for this kind of data is generated in a way that do not provoke collisions inter-installations, making thus possible to work different developers in different projects inserting data in the same tables at once. The way numbers are generated for these identifiers is having a different range for each development environment (it's called development environment ID).

Aim of the project

This project will affect all the tables in the application modifying their structure to be able to store UUIDs as primary key as well as all the queries to these tables.

Impact in the application

Test cases


Retrieved from ""

This page has been accessed 5,663 times. This page was last modified on 3 April 2012, at 11:01. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.