This topic is locked
[SOLVED]

 Schema name prepended

11/19/2009 9:16:35 AM
PHPRunner General questions
W
wpl author

Hi,
when a join of two tables is involved, PHPRunner will prepend the schema and table name to all fieldnames like this:
SELECT

"public".table1.field1,

"public".table1.field2,

"public".table2.field1,

"public".table1.field3,

....
Thus, updating a record will fail with the error msg:
ERROR: column "public" of relation "xxx" does not exist.
If I remove "public" manually, I get:
ERROR: column "table1" of relation "xxx" does not exist
What am I supposed to do to avoid this?
TIA

J
Jane 11/20/2009

Him
unfortunately PHPRunner do not support to update two tables at the same time.

Use Before record added/Before record updated events for this purpose:

http://www.xlinesoft.com/phprunner/docs/update_multiple_tables.htm

W
wpl author 11/21/2009



Him
unfortunately PHPRunner do not support to update two tables at the same time.

Use Before record added/Before record updated events for this purpose:

http://www.xlinesoft.com/phprunner/docs/update_multiple_tables.htm


Jane,
thanks for answering. Maybe I should have been more specific.... The problem ist not about updating data in two tables, updating occurs just in one table. The one (and only) field from the second table is for displaying data from this field on the list page only. It is n o t configured for edit and add pages. But, when data in other fields (from table 1!) is changed and tried to save, the mentioned error happens. If I debug the application, I can see that the sqlstring for the update does not contain references to table 2.
thanks

J
Jane 11/24/2009

Could you publish your project on Demo Account and open a ticket at http://support.xlinesoft.com sending a URL to your pages along with instructions on reproducing this error?

W
wpl author 11/25/2009



Could you publish your project on Demo Account and open a ticket at http://support.xlinesoft.com sending a URL to your pages along with instructions on reproducing this error?


Jane,
thanks for your continuing support. I think I will go for writing my own save handlers in the "Before record added/Before record updated" events as you previously suggested.
thanks