Hi Paul,
Just a quick update from my end. The second query that was creating an error now seems to be working (although it may be worth noting that Stardog didn't seem to detect the changes in the databases until I removed and re-added the data sources).
Thanks again for your help!
Megan
Did you change the databases? If the schema changes then a refresh is required. We cache the metadata (tables, columns, etc) for performance purposes. You can use stardog-admin data-source refresh-metadata ds_name to replace the cached metadata.
Also, if you did make a change, will I need it for these new mappings to work?
Thanks,
-Paul
Hi Paul,
Yes - we did make changes to the databases (namely, changing the defined column types as a temporary solution).
Thanks for the pointer to that command, that will be useful in the future!
The updated mappings will work with the original database backups (they don't work with the newer versions). But, as I mentioned - everything seems to be resolved with the workaround for now (now that I've refreshed)!
Great! Thanks, -Paul