I am sure someone has run into this… but I searched this forum and didn’t see it mentioned.
I just generated the security sample and am getting an error when I try to run it.
I think its missing some tables?
I think I just found the problem… the table is there but it must be case sensitive since its in lower case and the SQL statement is referencing an upper case table name.
This is a setting in MySQL that I will need to resolve on my own.
Might be good to document that your MySQL server should be setup to ignore case.
Hello,
Issue reported to our bugs team.
regards,
Bernhard Bernsmann
Hello,
Some assumptions have to try to know what this problem may have occurred.
I would like you to answer some questions:
1 - What is your database?
2 - The SQL that creates tables are in uppercase? (table name)
You can check on database builder if table names are in uppercase.
SQL option in the application, there is also enabling the Case Sensitive SQL code. Try this too. (See image)
Thank you!
The issue is that by default MySQL is standard case sensitive on table names. The issue is there in your samples (ie. webshop) too. This default behaviour started when Oracle took over, but despite that, Scriptcase should be consistent in naming tables in upper or lowercase, but not mixed.
Hello,
a partial solution to the problem is to create the log table in uppercase.
Worked normal for me.
By the way, this problem is already in the development sector to be fixed.
See the attached image.
Thank you!
The issue is consistancy. If you use lowercase tables somewhere else, i.e. the reporting app then you will run into issues on another spot. So - or do all in lowercase, or do all in uppercase. Same goes for your samples, there are inconsistancies also. In this case it’s an odd solution as the application should use the name of the table which is entered here. So if someone enters it lowercase, it should be used lowercase throughout the application.
Hello,
This problem has solved in last Scriptcase Update (8.0.015).
If you try again and get same error, please contact us again.
Thank you!