From: | Navnath Gadakh <navnath(dot)gadakh(at)enterprisedb(dot)com> |
---|---|
To: | Dave Page <dave(dot)page(at)enterprisedb(dot)com> |
Cc: | Kanchan Mohitey <kanchan(dot)mohitey(at)enterprisedb(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Server specific advanced config file for testsuite |
Date: | 2016-09-12 17:26:20 |
Message-ID: | CAOAJCYpsPXH3oKen-zH3oLjuOqdrt=XE4FiazYm0MsVQWtXk9g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi Dave,
As we know that, we are using two JSON files one is for basic
configuration of server(test_config.json) and second for detailed
configuration of server(test_advanced_config.json).
In test_advanced_config.json, we give detail for database, schema,
extension, collation etc. These details are generic I mean these details
are not server specific.
- Do we need to allow user to give server specific details?
If yes, there should be some identification(like ‘server_type’, ‘version’)
for each detail so that we can read server appropriate details.
We have one approach in mind, to attach 'server_type' & 'version' to each
detail
So, modified test_advanced_config.json can be like this,
{
"add_database_data”:[
{
"conn_limit": -1,
“owner”: “postres”,
.
.
.
.
“server_type”: “pg”,
“version”: “pg9.4”
},
{
{
"conn_limit": -1,
“owner”: “enterprisedb”,
.
.
.
.
“server_type”: “ppas”,
“version”: “ppas9.6”
}
}],
“schema_credentials”:
[{"func_acl": [],
"seq_acl": [],
.
.
.
.
“server_type”: “pg”,
“version”: “pg9.4”
}]
.
.
.
.
.
}
Any suggestions?
For multiple server currently we used 'owner' to identify the server, but
that fails if two servers have the same owner.
--
Thanks,
Navnath Gadakh
Software Engineer
EnterpriseDB Corporation
Mobile: +91 9975389878
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Brown | 2016-09-13 02:11:38 | PGAdmin 4 1.0-rc1 bugs |
Previous Message | Dave Page | 2016-09-12 14:21:18 | Re: Re: [pgAdmin4][Patch]: RM1683 - Reverse engineered SQL for function ALTERs/ACLs is incorrect with OUT parameters |