Details
Description
At the moment JDBCDataStore runs all the table creation statements using an auto committing connection, it would be better if a transaction was used.
Notice that not all databases supports transactions with DDL, but some do, like PostgreSQL for example. Not sure about the others, but afaik most will just ignore the transaction being set if they don't support transactional DDL. Worst case we can add a new method to the dialect...
As I pointed out some times ago, it is not possible to use a JDBCFeatureStore in a bigger transaction , manipulating classical tables and features within one transaction. Using autocommit is the same as using no transaction at all.
Whats your opinion about doing a redesign omitting the autocommit feature and making the JDBCFeatureStore more useable in complex environments?