Optional SQL Script inclusion.

[p35t173nc3]

Would it be possible to, based on an per build basis, include or exclude a SQL script in the installation? i.e. I would like to have a build of my installation that is for normal users and one for demo purposes; I would like the script that creates the demo database to only be included in the demo installation (I would like to set it up as a different build.)

Thanks again!
Daniel

[Cosmin]

Hi Daniel,

Unfortunately SQL scripts are not per-build. However, you can condition them with the "AI_BUILD_NAME" property. This way the script can run only for a specific build.

Regards,
Cosmin

[p35t173nc3]

I was hoping that perhaps you could allow for it to be per build. The reason being is that the script in question, compressed with maximum compression, is over 7Mb and I would rather not package it into all my installations...

[Cosmin]

Hi,

I added this improvement on our TODO list. Thank you for your suggestion. Until then you can try this workaround:
- in "SQL Scripts" page condition your full and demo scripts using AI_BUILD_NAME
- in "Table Editor" page select the "AI_SQLScript" table
- use "Build" combo on the toolbar to select the build which shouldn't contain the script
- change the ScriptText column to point to a dummy empty file

For example, the dummy file can be used as the:
- demo script in the full build
- full script in the demo build

This way an empty file is used for the build which shouldn't contain the script. The script condition will also make sure that this dummy file is not used.

Regards,
Cosmin

[p35t173nc3]

Thank you, thank you very much!

[Dan]

Hello,

This improvement has been added in version 11.0 of Advanced Installer released on March 13th, 2014.

Best regards,
Dan

[p35t173nc3]

Awesome, thanks!

[Dan]

You're welcome,

If you have other questions, please let us know.

Best regards,
Dan