Subscriber data entry screen should keep the entered
field values when save transaction fails. It should also
show which field(s) was/were the cause of the failure.
This is a critical bug that will prevent proper data entry.
The ID should not be included int he insert statement at all
(the
default value from the sequence should be used).
This should be checked for all crosslink tables ASAP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem still exists in the current CVS version.
Added a sequence and grant statements.
Remember to drop the database and users first before testing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1370748
See string:dataobject_subscriber_meterstatus: Query Error:
[db_error: message="DB Error: constraint violation" code=-3
mode=return level=notice prefix="" info="INSERT INTO
subscriber_meterstatus (id , subscriberid , codedvalue )
VALUES ( 1 , 5 , 3 ) [nativecode=ERROR: duplicate key
violates unique constraint "subscriber_meterstatus_pkey"]"]
Logged In: YES
user_id=30248
This is a critical bug that will prevent proper data entry.
The ID should not be included int he insert statement at all
(the
default value from the sequence should be used).
This should be checked for all crosslink tables ASAP.
Logged In: YES
user_id=30248
I guess the problem is caused by a missing grant statement.
Please check if grant statements are available for ALL sequences
in create_css_ddl.sql
Logged In: YES
user_id=30248
The problem still exists in the current CVS version.
Added a sequence and grant statements.
Remember to drop the database and users first before testing.
Logged In: YES
user_id=695149
Is this problem still appearing.
Logged In: YES
user_id=695149
This bug should be fixed with the form validation.Please
check in order to close.