Trying using $_ENV for database connection

[vv-a2007]

I'm trying to use the approach that Brian @Hyperbytes showed in his video

Managing Database connections via $_ENV variables

In this video we explore using the Server Connect settings "environment" tab to define database connection settings for workflow globals. PLEASE NOTE The Database manager settings for the production target are now editable (apparently this was actually a bug) and now the "hack" is no longer necessary. [Using $_ENV variables to define database connection settings]

I have defined environment variables, but when I try to use them - they are not in the parameter list - what could be the reason for this?

[famousmag]

I think you should define the ENV variables in your gloabls...

(Have in mind that ENV variables are defined per target)

[Hyperbytes]

You are correct, ENV vars are per target so need to be defined in both targets with their resective settings.

Also yes, they must be defined in globals to appear in the picker

[vv-a2007]

Thanks for the advice, I added these parameters and entered the data based on them in the settings of the connections for development and production. But the actual connection in development does not change to that set by variables.

[famousmag]

2 diferrent things @vv-a2007...

Check out here:

Direct Database connection with dynamic values

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.

[vv-a2007]

it became a little clearer - but the interface logic is very strange

[Hyperbytes]

Wappler plans a full revamp of target settings in wappler 7

[vv-a2007]

@famousmag Let's say there were changes in the structure and fields in my test database. And if I want to use these fields in queries in SC, should I connect the test database in the Database Manager section?

[Teodor]

If you made these changes with some external db management software, outside of Wappler, then you simply need to right click the table name and refresh it:

The new fields will appear.

[vv-a2007]

The point is that during the development process, test changes first appear in the database structure, which I need to use in Wappler. Then they will be applied to the production base - but this is all done through external tools and by other developers.

[Teodor]

Not sure i really understand what do you mean, but in order to apply local db changes to the remote database from within Wappler, using the Database Manager, then you need to make the changes using the Database Manager.
Wappler is not aware of any changes you make outside it, so it can't keep track of them ...

[vv-a2007]

No, I don’t want Wappler to make changes to the structure, I just need it to see the new tables and fields so they can be used in queries

[Teodor]

@vv-a2007

I just need it to see the new tables and fields so they can be used in queries

As explained already:

@Teodor

If you made these changes with some external db management software, outside of Wappler, then you simply need to right click the table name and refresh it: