I know that i should not use that system table and i know that there are performance issues.
My question was how to find out by SQL if the record is locked by another transaction.
I need to know, when the update fails by the Apache side in order to display that to the user.
On our error lock...
by a PHP Application i want to update a dataset inside a Progress-Table, that is working generally.
But it is possible to work on the same dataset inside our EPR-System that locks the dataset. Now when i want to update the dataset this i get this error.
Now i found the -Mn and -n parameters. ProAplha has a tool where we can edit these parameters.
How we solve the problem that the broker will not detect dead server?
Errormessage "BROKER entdeckte toten Server" ( "broker detects death of server" )
Where this error comes from?
we have written an application where we are connecting to a progress database via ODBC and SQL. On the other side there is running an proAlpha application.
Our application is written in PHP and is running an a Debian Linux Server.
When we are executing a SQL statement...
we have an intranet website written by PHP. There we are using the odbc interface. Next to this website the customer is working with ProAlpha.
During the select statements these error messages are occurring:
[Mon Jul 20 11:48:13 2015] [error] [client 192.168.50.207] PHP...
I got the following error message:
SQL error: [unixODBC][DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Ung, SQL state S1000 in SQLExecDirect
Can anyone tell me, what this message means?
I have a php application which opens a database connection. The code looks like this and is working fine.
$strDSN = "progress_test01";
$strUsername = "user";
$strPassword = "xyz";
$_SESSION [ 'odbc_connect_01' ] = odbc_connect( $strDSN, $strUsername, $strPassword )...