I have faced one problem while importing a solution.
I got the error,
The auto enter types in the import are different from the auto enter types on existing tables for server ‘example_data’.
Do you wish to override the existing auto enter types? (Yes\No)
It means that the autoenter types like sequences, creation datetime, modification datetime, creation username, etc. in the release you are trying to import are different from the release already in production.
Answering yes you update the autoenter types with the ones specified in the new release, answering no you don’t update the autoenter types and the old ones remain effective.
Basically the only reason to answer “no” that I can think of is when you are using servoy sequences in the developer and db managed sequence in the production server or the opposite.
Dear Servoyans in Engineering reading this thread,
Per earlier posts (about a month or so ago) on this topic, please consider breaking out the Servoy sequences from the other autoenter settings being altered via an import.
With larger install bases, it will become critical to leave these Servoy managed sequences intact while the production “application layer/server(s) are being quickly bumped (stop, restart) for a new release”.
Appreciate your reflection on this topic … there are definitely some advantages to using Servoy managed pk sequences in some environments … like certain flavours of SAAS.