2. PHPRunner General questions
  3. [SOLVED]   ORA-00972: identifier is too long
This topic is locked
[SOLVED]

  ORA-00972: identifier is too long

 		4/13/2012 6:55:39 AM
PHPRunner General questions
S
 scopley author

I'm receiving the ORA-00972: identifier is too long error message on a couple of my queries. I was wondering if there was a way to tell PHPRunner NOT to include the schema name in it's queries? If I manually delete the schema name the queries work fine every time.
Renaming the tables to something shorter at this point is not an option.
Thanks in advance for your help.
Sarah
S
 		scopley author 4/16/2012



I'm receiving the ORA-00972: identifier is too long error message on a couple of my queries. I was wondering if there was a way to tell PHPRunner NOT to include the schema name in it's queries? If I manually delete the schema name the queries work fine every time.
Renaming the tables to something shorter at this point is not an option.
Thanks in advance for your help.
Sarah


Also this was an existing project that was done in PHPRunner 5.1. We just recently upgraded to PHPRunner 6.0 Build 9948. That's when the problem started.
Sarah
Sergey Kornilov admin 4/25/2012

This error happens when PHPRunner counts the number of detail records while displaying your List page.

It modifies the SQL query and accidentally creates identifiers too long for Oracle.

There are two ways to get it working.

  1. Disable child record counting in PHPRunner. In order to do this open Datasource Tables tab in PHPRunner and double-click the links connecting SERVICES_REQUEST with other tables. Uncheck both "Display a number of child records" and "Hide detail link..." boxes in all the links.

  2. You can leave the above options on but change the counting method to another one without SQL query modifications involved.

    Add the following code to 'After application initialized' event:

    -------------------------------------------------

    $bSubqueriesSupported=false;