You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have an extension with 2 other extensions listed as required in the control file.
When I try to load the extension into a database with pgxn, these extensions must be already created to avoid an error.
If the CASCADE clause would be added to the CREATE EXTENSION statement issued by pgxn, it would simplify the operation for users.
I don't see any drawback to have this clause systematically added. Otherwise a --cascade option, for instance, could be used as a switch.
Philippe.
The text was updated successfully, but these errors were encountered:
I don't have time to develop this feature in my free time. If you would like to fund the development please let me know. I am open to receive merge requests if you want to develop the feature on your own.
As I am now retired and only develop on my free time, I cannot fund such a development. And I have not the needed python knowledge to event suggest a merge request.
May be someone else could help ?
Hi,
I have an extension with 2 other extensions listed as required in the control file.
When I try to load the extension into a database with pgxn, these extensions must be already created to avoid an error.
If the CASCADE clause would be added to the CREATE EXTENSION statement issued by pgxn, it would simplify the operation for users.
I don't see any drawback to have this clause systematically added. Otherwise a --cascade option, for instance, could be used as a switch.
Philippe.
The text was updated successfully, but these errors were encountered: