Hi,

First of all a rough sketch of what I'm are trying to do: For my company I'm using LLBLGen Pro 2.0 to work with a Postgresql database. This database is used by several code-bases in different languages. At the moment we are doing some major refactoring of the database. We have split the database into several schema's and each schema translates to a different namespace in code, so now I have a different project for each namespace. It should be possible for the users of our product to add such schema's themselves, and call some sort of webservice that will generate a dll they can import into the product.

Now to do this, I have some questions: 1/ Is it possible to create a new project (.lgp) using the sdk. Otherwise the only way I see to automate generating each project is to use an empty .lgp project with all properties set and run that through the cli tools to refresh the catalog and generate the code. Is this assumption correct or is there a better way?

2/ In case I have to use the empty .lgp project, is there any way to specify the database/host/login/password to use for refreshing the catalog via commandline parameters?

3/ Some tables have a reference to a table in another namespace. These relations are no longer enforced on database level, because they can be in different databases. In some predefined cases though I would still like to have the related properties in the generated code. Do you have any suggestion on how to best achieve this? The only way I see is to do some post-generation of my own (maybe using a custom task) that generates these properties.

Thanks, Rick

vanoverr wrote:

Hi,

First of all a rough sketch of what I'm are trying to do: For my company I'm using LLBLGen Pro 2.0 to work with a Postgresql database. This database is used by several code-bases in different languages. At the moment we are doing some major refactoring of the database. We have split the database into several schema's and each schema translates to a different namespace in code, so now I have a different project for each namespace. It should be possible for the users of our product to add such schema's themselves, and call some sort of webservice that will generate a dll they can import into the product.

Now to do this, I have some questions: 1/ Is it possible to create a new project (.lgp) using the sdk. Otherwise the only way I see to automate generating each project is to use an empty .lgp project with all properties set and run that through the cli tools to refresh the catalog and generate the code. Is this assumption correct or is there a better way?

You need the designer to create a project.

2/ In case I have to use the empty .lgp project, is there any way to specify the database/host/login/password to use for refreshing the catalog via commandline parameters?

You can by altering the sourcecode a bit.

3/ Some tables have a reference to a table in another namespace. These relations are no longer enforced on database level, because they can be in different databases. In some predefined cases though I would still like to have the related properties in the generated code. Do you have any suggestion on how to best achieve this? The only way I see is to do some post-generation of my own (maybe using a custom task) that generates these properties.

With Another namespace you mean another project ? If so, then yes, you need a custom task and a template which utilizes this.