IntenseWebs/pgadmin4
3
0
Fork 0
mirror of https://github.com/pgadmin-org/pgadmin4.git synced 2025-02-10 23:45:58 -06:00
Code Issues Packages Projects Releases Wiki Activity
8480c10c74
pgadmin4/web/pgadmin/browser/server_groups/servers/ppas.py

27 lines
809 B
Python
Raw Normal View History

Changed the logic to identify the PostgreSQL server variant, when we connect to the database server. Also, added modified the way, we do check the node is supported by the server. Instead of creating separate blueprint for the server types, they will be independently works. In order to add different variant of the PostgreSQL, we need to extend the ServerType class, and override the 'instanceOf' function for identification using version string. Please take a look at the ppas.py for the example. During checking the back-end support for the node, we will also check the server type (variant) along with the version within the range of maximum and minimum version for the node. And, the same support added for the schema attributes in front-end (JavaScript). Really thankful to Khushboo Vashi for her initial work in front-end. I took it further from there.
2015-11-19 11:45:48 -06:00
##########################################################################
#
# pgAdmin 4 - PostgreSQL Tools
#
Update copyright notices for 2018.
2018-01-05 04:42:49 -06:00
# Copyright (C) 2013 - 2018, The pgAdmin Development Team
Changed the logic to identify the PostgreSQL server variant, when we connect to the database server. Also, added modified the way, we do check the node is supported by the server. Instead of creating separate blueprint for the server types, they will be independently works. In order to add different variant of the PostgreSQL, we need to extend the ServerType class, and override the 'instanceOf' function for identification using version string. Please take a look at the ppas.py for the example. During checking the back-end support for the node, we will also check the server type (variant) along with the version within the range of maximum and minimum version for the node. And, the same support added for the schema attributes in front-end (JavaScript). Really thankful to Khushboo Vashi for her initial work in front-end. I took it further from there.
2015-11-19 11:45:48 -06:00
# This software is released under the PostgreSQL Licence
#
##########################################################################
Copyright updates for 2016.
2016-01-18 08:48:14 -06:00
Update Python and JS modules. Fixes #3154
2018-04-04 04:47:01 -05:00
from flask_babelex import gettext
Changed the logic to identify the PostgreSQL server variant, when we connect to the database server. Also, added modified the way, we do check the node is supported by the server. Instead of creating separate blueprint for the server types, they will be independently works. In order to add different variant of the PostgreSQL, we need to extend the ServerType class, and override the 'instanceOf' function for identification using version string. Please take a look at the ppas.py for the example. During checking the back-end support for the node, we will also check the server type (variant) along with the version within the range of maximum and minimum version for the node. And, the same support added for the schema attributes in front-end (JavaScript). Really thankful to Khushboo Vashi for her initial work in front-end. I took it further from there.
2015-11-19 11:45:48 -06:00
from pgadmin.browser.server_groups.servers.types import ServerType
class PPAS(ServerType):
Ensure database driver names and description strings can be translated. Fixes #2190
2017-04-18 07:33:27 -05:00
UTILITY_PATH_LABEL = gettext("EDB Advanced Server Binary Path")
UTILITY_PATH_HELP = gettext(
"Path to the directory containing the EDB Advanced Server utility"
" programs (pg_dump, pg_restore etc)."
)
Changed the logic to identify the PostgreSQL server variant, when we connect to the database server. Also, added modified the way, we do check the node is supported by the server. Instead of creating separate blueprint for the server types, they will be independently works. In order to add different variant of the PostgreSQL, we need to extend the ServerType class, and override the 'instanceOf' function for identification using version string. Please take a look at the ppas.py for the example. During checking the back-end support for the node, we will also check the server type (variant) along with the version within the range of maximum and minimum version for the node. And, the same support added for the schema attributes in front-end (JavaScript). Really thankful to Khushboo Vashi for her initial work in front-end. I took it further from there.
2015-11-19 11:45:48 -06:00
def instanceOf(self, ver):
return ver.startswith("EnterpriseDB")
Code tidy.
2016-06-21 08:21:06 -05:00
Changed the logic to identify the PostgreSQL server variant, when we connect to the database server. Also, added modified the way, we do check the node is supported by the server. Instead of creating separate blueprint for the server types, they will be independently works. In order to add different variant of the PostgreSQL, we need to extend the ServerType class, and override the 'instanceOf' function for identification using version string. Please take a look at the ppas.py for the example. During checking the back-end support for the node, we will also check the server type (variant) along with the version within the range of maximum and minimum version for the node. And, the same support added for the schema attributes in front-end (JavaScript). Really thankful to Khushboo Vashi for her initial work in front-end. I took it further from there.
2015-11-19 11:45:48 -06:00
# Default Server Type
String improvements.
2016-06-17 08:35:16 -05:00
PPAS('ppas', gettext("EDB Advanced Server"), 2)
Reference in New Issue Copy Permalink