>From the server job log (edited):
Message ID . . . . . . : SQL7008 Severity . . . . . . . :
30
Message . . . . : PERSON in QGPL not valid for
operation.
Cause . . . . . : The reason code is 3. Reason codes and their
meanings
are:
3 -- PERSON not journaled, or no authority to the journal. Files
with an
RI constraint action of CASCADE, SET NULL, or SET DEFAULT must be
journaled
to the same
journal.
Recovery . . . : Do one of the following based on the reason
code:
3 -- Start journaling on PERSON (STRJRNPF), or get access to the
journal.
This could be due to:
1) Journaling is off but there is a commitment control requirement.
2) There is a bug. There are several reports with this message & code.
I am going to test on another server with a newer OS (V5R3), this one
is running V5R2 with maintenance level TL06080 (a few years old).
carlo, if you have access to a newer one you can test too, modify
sql.py rev745 as follows:
line 295
'id': 'INTEGER GENERATED ALWAYS AS IDENTITY PRIMARY KEY NOT NULL',
line 296
'reference': 'INT, FOREIGN KEY (%(field_name)s) REFERENCES %
(foreign_key)s ON DELETE %(on_delete_action)s',
line 789
self._execute = lambda a: self._cursor.execute(a[:-1])
Denes.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
