Description
In both SQL Server and Oracle we can create autonumber integer fields for primary keys. We use it also. But we need always to change the generated SQL Server Procs for insert and create for Oracle a sequence trigger Can Uniface implement this in the entities as a field type?
Use Case
Importance
Type
Database Drivers
Operating System
Not Applicable
Status
Open
I think this request could be referred to the wish I’ve raised in this page:
and to the one referred from Iain Sharp in the comments of it…
autonumber = packing code A = support for technical keys
we need a global portable solution to this functionality…
Sorry but something went wrong with HTML tags and attributes in the previous post!!!
I think this request could be referred to the wish I’ve raised in this page:
http://unifaceinfo.com/packing-code-a-for-all-dbms-drivers/
and to the one referred from Iain Sharp in the comments of it…
autonumber = packing code A = support for technical keys
we need a global portable solution to this functionality…
As well as what is mentioned in the linked wishlist case, you could also do something that we have done….
(we were using Sybase Identity columns)
Write yourself a little Uniface code or shell script to parse your Uniface generated SQL proc and add your identity column definitions in the SQL.
You would then be able to modify your errorField triggers to handle (looking for 0129) the NULL in your PK values on STORE, and have your DB do the rest.