Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Don Ignacio — — source: Informix-list mailing list archive (1991-1998)
Hi,
You have several options:
1. You can set the session to FILTERING mode in order to insert the SQL
statement
into the violations table.
2. You can place DISPLAY statement in the 4GL code to show the SQL
statement
3. If the primary key is program generated you can look at the code
4. If it is entered by the user, ask the user what primary key they are
entering :-)
Don
"Adam:-)" wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dear Knowledgable,
> I am running Informix IDS 7.31UC5 on AIX 4.3.3. My problem is one
> of the users has managed to bypass the application and entered a
> record into a table(yet to be worked out how this was done) The only
> problem is that the application (written in 4gl) can not carry out an
> insert due to a duplicate primary key.
> Q. How can I get the IDS engine to tell me what value the
> application is trying to insert into the table as when I run
> "onstat -g ses thread ID" I can view the SQL but it just has ? marks
> for the values. If I new what the values were I could remove the
> record from the table and hence enable the application to continue
>
> Adam Birch
> ambirch@hotmail.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>
>
> iQA/AwUBOU11b3QB7atCA4drEQLYNwCdG6kkOVZyHWLpfdJF3/wM+Wof1IEAn1Y8
> bcq70gPtD04CiTE8ZYU21Qfu
> =R+Mu
> -----END PGP SIGNATURE-----
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.