Orbeon Forms 2018.1.1 CE & MySQL: 'Error performing search' received on summary page of any created form
I have installed Orbeon Forms 2018.1.1 CE using Mysql as a relational database (Mysql version: 8.0.13).
Although I am able to create, save and publish any form, when I try to access the summary of a form, I get an 'Error performing search' error. The same error is also displayed every time I try to search for a form on the summary page using the 'Search Forms' control on the upper section of the page.
In addition to that, the summary page is always empty, although the relevant table in the database contains the appropriate records. The application is running on the Apache Tomcat (8.5.35) and the database was created using the mysql-2017_2.sql script.
I have also checked the orbeon.log file and I've found the following entry:
An Error has Occurred
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to
use nearrow_number FROM orbeon_i_current c, (select @rownum := 0) rat line 12
Application Call Stack
oxf:/apps/fr/page-flow.xml
reading page view data output 46
element=
<service path="/fr/service/(oracle|mysql|postgresql|db2|sqlserver)/search/([^/^.]+)/([^/^.]+)" view="persisten view=persistence/relational/search.xpl
oxf:/apps/fr/persistence/relational/search.xpl
reading processor output 22
element=
<p:output name="data" ref="data"/>
name =data
ref =data
I am wondering if there is any other required configuration for the summary page to work properly.
Using the P6Spy application, I've realized that the following query seems to be responsible for the error message:
SELECT count(*)
FROM (
SELECT c.data_id,
c.document_id,
c.draft,
c.created,
c.last_modified_time,
c.last_modified_by,
c.username,
c.groupname,
c.organization_id,
@rownum := @rownum + 1 row_number
FROM orbeon_i_current c
, (select @rownum := 0) r
WHERE c.app = 'DemoApp' AND
c.form = 'DemoForm'
AND c.draft = 'N'
) a
Actually, the problem is probably in the line:
@rownum := @rownum + 1 row_number
MySQL introduced the window function ROW_NUMBER() since version 8.0 and in this line the literal 'row_number' is translated by the sql engine as a function.
mysql orbeon
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have installed Orbeon Forms 2018.1.1 CE using Mysql as a relational database (Mysql version: 8.0.13).
Although I am able to create, save and publish any form, when I try to access the summary of a form, I get an 'Error performing search' error. The same error is also displayed every time I try to search for a form on the summary page using the 'Search Forms' control on the upper section of the page.
In addition to that, the summary page is always empty, although the relevant table in the database contains the appropriate records. The application is running on the Apache Tomcat (8.5.35) and the database was created using the mysql-2017_2.sql script.
I have also checked the orbeon.log file and I've found the following entry:
An Error has Occurred
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to
use nearrow_number FROM orbeon_i_current c, (select @rownum := 0) rat line 12
Application Call Stack
oxf:/apps/fr/page-flow.xml
reading page view data output 46
element=
<service path="/fr/service/(oracle|mysql|postgresql|db2|sqlserver)/search/([^/^.]+)/([^/^.]+)" view="persisten view=persistence/relational/search.xpl
oxf:/apps/fr/persistence/relational/search.xpl
reading processor output 22
element=
<p:output name="data" ref="data"/>
name =data
ref =data
I am wondering if there is any other required configuration for the summary page to work properly.
Using the P6Spy application, I've realized that the following query seems to be responsible for the error message:
SELECT count(*)
FROM (
SELECT c.data_id,
c.document_id,
c.draft,
c.created,
c.last_modified_time,
c.last_modified_by,
c.username,
c.groupname,
c.organization_id,
@rownum := @rownum + 1 row_number
FROM orbeon_i_current c
, (select @rownum := 0) r
WHERE c.app = 'DemoApp' AND
c.form = 'DemoForm'
AND c.draft = 'N'
) a
Actually, the problem is probably in the line:
@rownum := @rownum + 1 row_number
MySQL introduced the window function ROW_NUMBER() since version 8.0 and in this line the literal 'row_number' is translated by the sql engine as a function.
mysql orbeon
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This might be a bug. Could you setup P6Spy as described here, and reproduce the problem to find the specific SQL query that is causing the issue? Then it would be useful if you could post it in a comment, or update your question to mention the source of that query. You'll let us know what you find.
– avernet
Dec 27 at 22:23
I have updated my question with the findings of using the P6Spy. It seems to be a bug.
– George Papageorghiou
2 days ago
Thank you for the investigation. And indeed, I think you put your finger on the issue. So for now you won't be able to use MySQL 8. But I've created issue 3864, and we'll shoot to fix this for 2018.2.1.
– avernet
yesterday
add a comment |
I have installed Orbeon Forms 2018.1.1 CE using Mysql as a relational database (Mysql version: 8.0.13).
Although I am able to create, save and publish any form, when I try to access the summary of a form, I get an 'Error performing search' error. The same error is also displayed every time I try to search for a form on the summary page using the 'Search Forms' control on the upper section of the page.
In addition to that, the summary page is always empty, although the relevant table in the database contains the appropriate records. The application is running on the Apache Tomcat (8.5.35) and the database was created using the mysql-2017_2.sql script.
I have also checked the orbeon.log file and I've found the following entry:
An Error has Occurred
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to
use nearrow_number FROM orbeon_i_current c, (select @rownum := 0) rat line 12
Application Call Stack
oxf:/apps/fr/page-flow.xml
reading page view data output 46
element=
<service path="/fr/service/(oracle|mysql|postgresql|db2|sqlserver)/search/([^/^.]+)/([^/^.]+)" view="persisten view=persistence/relational/search.xpl
oxf:/apps/fr/persistence/relational/search.xpl
reading processor output 22
element=
<p:output name="data" ref="data"/>
name =data
ref =data
I am wondering if there is any other required configuration for the summary page to work properly.
Using the P6Spy application, I've realized that the following query seems to be responsible for the error message:
SELECT count(*)
FROM (
SELECT c.data_id,
c.document_id,
c.draft,
c.created,
c.last_modified_time,
c.last_modified_by,
c.username,
c.groupname,
c.organization_id,
@rownum := @rownum + 1 row_number
FROM orbeon_i_current c
, (select @rownum := 0) r
WHERE c.app = 'DemoApp' AND
c.form = 'DemoForm'
AND c.draft = 'N'
) a
Actually, the problem is probably in the line:
@rownum := @rownum + 1 row_number
MySQL introduced the window function ROW_NUMBER() since version 8.0 and in this line the literal 'row_number' is translated by the sql engine as a function.
mysql orbeon
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have installed Orbeon Forms 2018.1.1 CE using Mysql as a relational database (Mysql version: 8.0.13).
Although I am able to create, save and publish any form, when I try to access the summary of a form, I get an 'Error performing search' error. The same error is also displayed every time I try to search for a form on the summary page using the 'Search Forms' control on the upper section of the page.
In addition to that, the summary page is always empty, although the relevant table in the database contains the appropriate records. The application is running on the Apache Tomcat (8.5.35) and the database was created using the mysql-2017_2.sql script.
I have also checked the orbeon.log file and I've found the following entry:
An Error has Occurred
You have an error in your SQL syntax; check the manual that
corresponds to your MySQL server version for the right syntax to
use nearrow_number FROM orbeon_i_current c, (select @rownum := 0) rat line 12
Application Call Stack
oxf:/apps/fr/page-flow.xml
reading page view data output 46
element=
<service path="/fr/service/(oracle|mysql|postgresql|db2|sqlserver)/search/([^/^.]+)/([^/^.]+)" view="persisten view=persistence/relational/search.xpl
oxf:/apps/fr/persistence/relational/search.xpl
reading processor output 22
element=
<p:output name="data" ref="data"/>
name =data
ref =data
I am wondering if there is any other required configuration for the summary page to work properly.
Using the P6Spy application, I've realized that the following query seems to be responsible for the error message:
SELECT count(*)
FROM (
SELECT c.data_id,
c.document_id,
c.draft,
c.created,
c.last_modified_time,
c.last_modified_by,
c.username,
c.groupname,
c.organization_id,
@rownum := @rownum + 1 row_number
FROM orbeon_i_current c
, (select @rownum := 0) r
WHERE c.app = 'DemoApp' AND
c.form = 'DemoForm'
AND c.draft = 'N'
) a
Actually, the problem is probably in the line:
@rownum := @rownum + 1 row_number
MySQL introduced the window function ROW_NUMBER() since version 8.0 and in this line the literal 'row_number' is translated by the sql engine as a function.
mysql orbeon
mysql orbeon
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Dec 28 at 12:54
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked Dec 27 at 14:25
George Papageorghiou
64
64
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
George Papageorghiou is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
This might be a bug. Could you setup P6Spy as described here, and reproduce the problem to find the specific SQL query that is causing the issue? Then it would be useful if you could post it in a comment, or update your question to mention the source of that query. You'll let us know what you find.
– avernet
Dec 27 at 22:23
I have updated my question with the findings of using the P6Spy. It seems to be a bug.
– George Papageorghiou
2 days ago
Thank you for the investigation. And indeed, I think you put your finger on the issue. So for now you won't be able to use MySQL 8. But I've created issue 3864, and we'll shoot to fix this for 2018.2.1.
– avernet
yesterday
add a comment |
This might be a bug. Could you setup P6Spy as described here, and reproduce the problem to find the specific SQL query that is causing the issue? Then it would be useful if you could post it in a comment, or update your question to mention the source of that query. You'll let us know what you find.
– avernet
Dec 27 at 22:23
I have updated my question with the findings of using the P6Spy. It seems to be a bug.
– George Papageorghiou
2 days ago
Thank you for the investigation. And indeed, I think you put your finger on the issue. So for now you won't be able to use MySQL 8. But I've created issue 3864, and we'll shoot to fix this for 2018.2.1.
– avernet
yesterday
This might be a bug. Could you setup P6Spy as described here, and reproduce the problem to find the specific SQL query that is causing the issue? Then it would be useful if you could post it in a comment, or update your question to mention the source of that query. You'll let us know what you find.
– avernet
Dec 27 at 22:23
This might be a bug. Could you setup P6Spy as described here, and reproduce the problem to find the specific SQL query that is causing the issue? Then it would be useful if you could post it in a comment, or update your question to mention the source of that query. You'll let us know what you find.
– avernet
Dec 27 at 22:23
I have updated my question with the findings of using the P6Spy. It seems to be a bug.
– George Papageorghiou
2 days ago
I have updated my question with the findings of using the P6Spy. It seems to be a bug.
– George Papageorghiou
2 days ago
Thank you for the investigation. And indeed, I think you put your finger on the issue. So for now you won't be able to use MySQL 8. But I've created issue 3864, and we'll shoot to fix this for 2018.2.1.
– avernet
yesterday
Thank you for the investigation. And indeed, I think you put your finger on the issue. So for now you won't be able to use MySQL 8. But I've created issue 3864, and we'll shoot to fix this for 2018.2.1.
– avernet
yesterday
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
George Papageorghiou is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53946594%2forbeon-forms-2018-1-1-ce-mysql-error-performing-search-received-on-summary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
George Papageorghiou is a new contributor. Be nice, and check out our Code of Conduct.
George Papageorghiou is a new contributor. Be nice, and check out our Code of Conduct.
George Papageorghiou is a new contributor. Be nice, and check out our Code of Conduct.
George Papageorghiou is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53946594%2forbeon-forms-2018-1-1-ce-mysql-error-performing-search-received-on-summary%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This might be a bug. Could you setup P6Spy as described here, and reproduce the problem to find the specific SQL query that is causing the issue? Then it would be useful if you could post it in a comment, or update your question to mention the source of that query. You'll let us know what you find.
– avernet
Dec 27 at 22:23
I have updated my question with the findings of using the P6Spy. It seems to be a bug.
– George Papageorghiou
2 days ago
Thank you for the investigation. And indeed, I think you put your finger on the issue. So for now you won't be able to use MySQL 8. But I've created issue 3864, and we'll shoot to fix this for 2018.2.1.
– avernet
yesterday