I don't know if this is feasible, however I was thinking that it would be nice to be able to define the DDL for custom tables and other SQL resources within Ignition, which Ignition would then use to create those objects if they don't already exist.
This would save having to write this into your script libraries for your custom table definitions and would provide a central location to house them. This would make it far simpler to also restore objects within a database, with the definitions all stored within the gateway backup to better support a single source of configuration.
It does, and I actually had the idea of exposing it via scripting a long time ago.
At this point in time I'm hesitant to do so:
I'm not sure how well our homegrown abstraction holds to public scrutiny - obviously it works okay for historian, SQL bridge, and others, but it won't do all the things for all the people - just what we've needed it to do over time.
Making it public API makes it a lot stricter to maintain. It's easy for us to evolve a Java interface/contract over time and we only have to worry about basic ABI compatibility within a minor version. Once it becomes part of a scripting interface, it's a lot harder to migrate.
