There should be a button in the dataprovider menu that connects to the database and checks that all of the table and field names and types are up to date.
While you are at it, you should flush the drivers being used, however that would require re-reading the .properties file which you have been shying away from.
flushing drivers won’t happen. Then we have to deal with class load issues of java. And when you update a driver (which won’t happen very often) one restart isn’t that much hassle…
gotcha, how about the database refresh?
what do you mean with database refresh?
All the data you have must be refreshed??
The data refresh is already implemented with loadallrecords.
I am referring to the Database Structure in Dataproviders. If I rename a field I am forced to restart servoy to have that change reflected.
If you change dataproviders within Servoy, you will see the changes at once, if changed externally you must restart, meta description kan be sent in the past to running Servoy clients
It seems you can rename global or calculation fields while in Servoy,
but not your regular column fields.
If you change a name externally, you will have to restart Servoy
AND reassign all dataproviders on all forms using the changed field… somewhat painful. “Data refresh” probably doesn’t solve this, Better to
add support for changing column names in the dataprovider dialog.
---- related field topic/feature request -----
I notice Servoy doesn’t seem to preserve case on normal column
fields, converting all to lower case. For me this ends up
being a minor issue when I export to XML, where I would like the XML
dataprovider attributes to preserve the actual backend field names.
hannawell:
It seems you can rename global or calculation fields while in Servoy,
but not your regular column fields.If you change a name externally, you will have to restart Servoy
AND reassign all dataproviders on all forms using the changed field… somewhat painful. “Data refresh” probably doesn’t solve this, Better to
add support for changing column names in the dataprovider dialog.
correct, column rename is not supported by all databases it is not in the SQL92 spec. (so its hard to offer in Servoy)
hannawell:
---- related field topic/feature request -----I notice Servoy doesn’t seem to preserve case on normal column
fields, converting all to lower case. For me this ends up
being a minor issue when I export to XML, where I would like the XML
dataprovider attributes to preserve the actual backend field names.
We could show the real SQL names, but that whould mix those with the lowercap names from globals/calcs, I’m not sure if thats the wanted behaviour.
Thanks Jan,
Jan Blok:
correct, column rename is not supported by all databases it is not in the SQL92 spec. (so its hard to offer in Servoy)
Couldn’t you still support it by creating a new column, copying data, editing dataprovider connections, and deleting the original column? Basically a developer/admin convenience feature…
Jan Blok:
We could show the real SQL names, but that whould mix those with the lowercap names from globals/calcs, I’m not sure if thats the wanted behaviour.
For me, the readability of all fields is more important than differentiating globals/calc fields. Maybe you could use a different font/style for global/calc fields.
hannawell:
Basically a developer/admin convenience feature…
We will consider this
hannawell:
Jan Blok:
We could show the real SQL names, but that whould mix those with the lowercap names from globals/calcs, I’m not sure if thats the wanted behaviour.For me, the readability of all fields is more important than differentiating globals/calc fields. Maybe you could use a different font/style for global/calc fields.
I was under the impression you where refering to printXML? but you are not?
Jan Blok:
hannawell:
Basically a developer/admin convenience feature…
We will consider this
quote]
I would love this! wit a total rename in the solution!
Jan Blok:
I was under the impression you where refering to printXML? but you are not?
You are correct, I am most concerned w/ getting the original names out w/ printXML.
Servoy’s onscreen field names display behavior is not so important, just a preference and belongs in a different thread. I guess I wasn’t sure there was some connection w/ printXML.
Your post confuses me, could specify what is wrong/missing in the XML produced by Servoy?
Jan Blok:
Your post confuses me, could specify what is wrong/missing in the XML produced by Servoy?
eg. I have a column in mySql db called “assetName”. Servoy’s XML export
for one entry:
I’d like to see ‘…dataprovider=“assetName”…’ or perhaps an additional
attribute to specify the actual backend column name.