Direct Database connection with dynamic values

[pixlapps]

When I create a new target in project options and want to add a custom database, I do not get the option to add dynamic values.

If I choose not to add a database and then go to the database manager and click direct database connect, I do not get dynamic options to insert

When I go to Resource manager it seems one can only add a locally used “new” database and not a directly connected one. Maybe I am wrong here, but from the parameters provided and one have to provide, I wasn’t able to connect to my database from there. Seems like it docker hosted databases you create from there

If I go to globals and go to the db settings there I get dynamic option available to me, BUT ADDING THEM MAKES NO DIFFERENCE AS IT SEEMS THEY ARENT USED IN MY SELECTED TARGET

For me the database connection management in Wappler is one of the things with the most broken user experience as there are multiple UI’s. places you can change and you do not know which one is used by your current target.

All I want to do is set up a direct database connection that takes dynamic values. Can I do that with Wappler? The UI definitely insinuate it, but it is not working for me.

[bpj]

The direct connection is for a fixed set of details that are used by the Wappler UI to run queries and fetch schema while building APIs. The connection that is used when the API file is running (and therefore has the dynamic data available) is under global>database and can have dynamic data using the binding tool.

[pixlapps]

Thanks, my problem is that it does not look like the global db option is being used.

How do I know which database connection settings are currently being used by the current target?

[bpj]

Could you create a test SC API file to look for a value (using a SC API query) that you know is specific to a particular database and see what it returns? I use dynamic database connections all the time and haven’t had an issue yet…

[scalaris]

There’s some long-standing bugs in here that will hurt you if you have a variety of development, staging and production environments. You can’t be sure that your builds will carry over the intended database targets. We’ve started to circumvent this by building a manual ci/cd workflow that updates the appropriate configuration files for us.

It’s significant overhead but removes the risk of wappler getting it wrong.

This isn’t a criticism, simply a by-product of commercial success

[George]

@scalaris Your reply is not really helpful, which bug are you referring to and what does it have to do with dynamic connections?

Please try to stay on topic and don’t just add generic replies like “ there are bugs that can hurt you”

[scalaris]

On the contrary. I’m answering the question clearly asked - ‘How do I know which database connection settings are currently being used by the current target?’

And the reality is that you cannot reliably know based on how it is configured in wappler. Had we been aware of that previously, we would have saved hours of wasted effort figuring out there was an issue.

It is also why we invested time and money in building a solution that removes our reliance on wappler during the build cycle.

Instead of taking offence, one should see it as an commercial opportunity to develop.amd market tooling in this regard.

A flexible and robust ci/cd is an absolute necessity if Wappler has the ambition to be a wolrd class development environment.