Hi Robert
Thanks for your comments
This is not ideal/acceptable in the vertical market. I might end up with 200 clients all using the same solution. I post an update on my website, they download and import, this should be straightforward and consistent if all backend DB’s JDBC and Servoy versions are all the same.
Consistency for me is the key. I don’t want to check all these installations every time i post a new solution version that has some new number fields.
Hi Rodney,
I understand.
But do you realize you already have a problem because your solution is not optimized. You don’t have any indexes in your database.
Of course depending on your datamodel this might be a small or a very big issue.
Just offering different DML scripts for the most used database platforms might not be such a big issue. There are some nice tools around that can create those for you with the press of a button.
A user that runs a SQL server should very much be able to run such SQL script.
Just food for thought.
Hi Robert
I put the indexes in when i do the initial installation.
Can you point me to a link for these tools?
Thanks again.
jaleman:
Does this occurr on iAnywhere too or just mysql?
In our case, this happens with iAnywhere also, the problem is I can’t reproduce it at scratch. so once in a while it happens, where floats become numeric.
But also other things, like for example: installed a servoy-server for a customer, uploaded the solution.
Now a week later, I do some updates on the solution (I’m 100% sure nothing has changed at my backend) I upload the new version of the solution at the customer. Now this server complains, that fields, that are on the server numeric (8) are numeric (19) in the imported version.
it is inconsistence…
And I can’t get my fingers at it, why this happens.
rodneysieb:
Can you point me to a link for these tools?
Sure.
A quick roundup via google got me the following:
Hi
I agree Harjo. It is inconsistent that servoy creates a float field in developer but on import servoy will create that field as a decimal (19,0) number type!
rodneysieb:
HiI agree Harjo. It is inconsistent that servoy creates a float field in developer but on import servoy will create that field as a decimal (19,0) number type!
I don’t. Harjo mentions he can’t reproduce it and that he might have touched the backend outside of Servoy so I don’t agree that in his case it is within Servoy’s control.
Can you file an issue in our case system with the versions you use and a mini solution that shows the problem? We will then have our engineers look into it. Please also mention the JDBC driver used with Mysql they tend to be very different from version to version.
No Jan, I’m 100% sure I did not touch the back-end of Ianywhere! (I never do!)
I spend allready two days to create a sample-solution for you guys, but it is hard to reproduce it. It happens sometimes, and sometime I don’t see it for a long time.
the only thing I can show you now, is some fields I created in Servoy developer. (you have to believe me,I never touched the back-end)
in my quote table they are numeric
in my invoice table they are double.
(this is in my developer)
Double and numeric 19,8 are both floats so that looks perfect to me.