I managed to install this Forge.
I executed test run properly but it didn't work.
I set Timer as below.
I wonder where there is the issue.
Am I missing Timer settings?
It'd be nice if you could give me any ideas.
Hmm, I thought I removed the semicolons. Must have used the wrong version to upload. I just uploaded a new version. Thanks for your patience.
Please let me know if everything is ok now.
Best regards,
Paul
Thank you so much.
It works even in Oracle!
For now, everything is all right.
I'm sorry. I appreciate your help.
Best,
Hi Tsubasha,
Did you check the errorlogs? They should provide you with details on the error. Also did you follow the steps as described in the documentation?
Hi Paul,
Thanks.
I checked the detail. Here is the log.
It seems like ORA00933 error is happening.
SQL command not properly ended
Does this error look familiar with you?
I don't use any SQL widget in my server action for my BDD test.
I wonder where we are missing.
I'd appreciate it if you could give me any advice.
By the way, I followed the steps as described in the documentation.
Regarding Grant access to the application,
I set like this. Is that corerct?
I'm trying to test only "TestSuite2" for now.
I hope these images could be useful for the cause.
Sorry for the inconvenience.
Thanks
Hi Tsubasa,I fixed the error in version 1.1.2. There was a semicolon missing in an sql statement.
I appreciate your help.
I updated it and then I tried my test again, but It seems like I'm facing another error.
I check the log and actually I found another bug. Here it is.
I'm guessing this is another ORA-00933 error.
The error says ORA00933 SQL command not properly ended.
I wonder where another semicolon is missing.
Are you familiar with that?
By the way, I check just my BDD test suite I'm trying to test it. I can tell there is no issue on my test side.
I don't think it has huge data and it doesn't execute huge process. in my BDD test
Also, I'm sure this module will be very useful for BDD test. I'd like to make use of my work.
Thanks,
I wonder the error is similar to this post. I happened to discover it
#98
This is my hunch.
Thank you for updating your module version to 1.2.2. Appreciated.
Oracle has a different way of working with dates. I changed te action to have a separate SQL for Oracle. Please checkout the new version
Thank you for giving the new version!
However with all due respect, I got another issue. It's ORA-00907 error (missing right parenthesis).
I tried to execute my current test again. So I'm aware I don't add anything weird.
Do you have any ideas on this error?
I have a hunch that it seems to be happening in BDDFrameworkReporting_CS .
I'd appreciate your help.
Sorry about that.There's indeed a loose parenthesis. I'll upload a new version with this SQL:
DELETE FROM {BDDTestSuiteRun} WHERE {BDDTestSuiteRun}.[StartedOn] < to_date(@CleanUpBeforeDate,'YYYY-mm-DD HH:MM:SS');
Appreciated.
It probably feels like I happen to discover there are some similar SQL mistakes in other parts when I'm using it again, but I'd like to let you know if I face an issue while using this module.
I'll be in touch. That's great.
You're welcome! Sorry I'm not able to test it on an Oracle Server myself. Appreciate your feedback!
Thank you for updating your module.
I retried it with the current test suite.But I got another issue which is ORA-00933 error(SQL command not properly ended. ).
I wonder if the error seems like to be happening here.
Any ideas? Sorry.
I removed semicolon at the last and pressed "test" but I got this error.
Are you familiar with this matter?
Can you try this?
DELETE FROM {BDDTestSuiteRun} WHERE ({BDDTestSuiteRun}.[StartedOn] < to_date(@CleanUpBeforeDate,'YYYY-mm-DD HH:MM:SS'));
I tried it.
But I still got the error.
*Actually in case of SQL, I remove semicolon at the last and try it. If it has the semicolon, I will get ORA-00933 error.
Do you have any ideas on the cause?
Sorry for adding.
It seems like I'm getting ORA-00933 error here too.
The original SQL statement is this.
update {BDDTestSuite} SET {BDDTestSuite}.[IsProcessed] = 0 FROM {BDDTestSuite} WHERE ({BDDTestSuite}.[IsActive] = 1) AND ({BDDTestSuite}.[IsProcessed] = 1);
I removed the semicolon and test it but it doesn't work.
I'm looking into it and trying everything here but I can't figure out why this is happening.
I wonder if this SQL statement doesn't seem to work in Oracle.
* My BDDFrameworkReportingReactive module is the latest version.
I'm touching base with you about update statement.
I did this way, I solved it.
According to some information, update doesn't need "FROM".
It seems like to be fine regarding "update" statement.
However I'm still not sure about the error in "BDDTestSuiteRunsDeleteBeforeCleanupDateOracle" Action
Sorry for the inconvienence. I'll create a new version without the "from" in the sql.
Regards,
Can you try this statement? See https://www.techonthenet.com/oracle/errors/ora01810.php
DELETE FROM {BDDTestSuiteRun} WHERE {BDDTestSuiteRun}.[StartedOn] < to_date(@CleanUpBeforeDate,'YYYY-MM-DD HH:MI:SS');
I tried that way but I got this error.
I wonder if this means the value is wrong somewhere.
About this error, I'm asking other people too.
here is the post.My post.
I hope this will help you.
Also, I just run with this statement and I 'm getting the below ORA-01861 error.
It seems like we are still facing SQL issue here. I can't figure out why
This is a reminder.
In Oracle , I simply wrote this way, I got it right.
Is this fine?
That's exact the same as in the SQL Server SQL. Only I think It should be terminated with a semicolon
DELETE FROM {BDDTestSuiteRun} WHERE {BDDTestSuiteRun}.[StartedOn] < @CleanUpBeforeDate;
I'll create a new version with a separate cleanup timer. In the BDDFrameworkReporting_CS module
Actually, in Outsystems, it seems like it doesn't work in Oracle if you add a semicolon .
So if you are using Oracle, in that case, we don't need semicolon .
If someone with oracle is using this command
, they will get ORA00933 error. In fact, I got succeeded without semicolon.
This is the same also in SQL widget using "UPDATE" statement in other actions.
Just uploaded a new version with a separate timer for the cleanup. Can you check it please?
I think it's better to add if statement to check if it's Oracle in the below two parts here.
I mean , for someone using Oracle, you'd better add this if widget to check if it's Oracle.
Otherwise, they will get ORA-00933 error, and have to just remove semicolon.
If it's oracle, the process goes to SQL without semicolon, if not, it goes to SQL with semicolon.
Do you think about this?
In fact , I've updated it and retried it, but I got ORA-00933 error as the same as before. So now I just removed semicolon in only SQL widgets.
When I removed just semicolon, this module works!
That's because I'm using Oracle.