Fix naming inconsistency for the column and FTS parser modules. Fixes #1269

This commit is contained in:
Dave Page 2019-03-14 16:52:42 +00:00
parent 395d3cb545
commit 69ec460b60
40 changed files with 8 additions and 7 deletions

View File

@ -18,6 +18,7 @@ Features
Bug fixes Bug fixes
********* *********
| `Bug #1269 <https://redmine.postgresql.org/issues/1269>`_ - Fix naming inconsistency for the column and FTS parser modules.
| `Bug #3104 <https://redmine.postgresql.org/issues/3104>`_ - Improve a couple of German translations. | `Bug #3104 <https://redmine.postgresql.org/issues/3104>`_ - Improve a couple of German translations.
| `Bug #3995 <https://redmine.postgresql.org/issues/3995>`_ - Avoid 'bogus varno' message from Postgres when viewing the SQL for a table with triggers. | `Bug #3995 <https://redmine.postgresql.org/issues/3995>`_ - Avoid 'bogus varno' message from Postgres when viewing the SQL for a table with triggers.
| `Bug #4019 <https://redmine.postgresql.org/issues/4019>`_ - Update all Python and JavaScript dependencies. | `Bug #4019 <https://redmine.postgresql.org/issues/4019>`_ - Update all Python and JavaScript dependencies.

View File

@ -13,7 +13,7 @@ import json
import uuid import uuid
from pgadmin.browser.server_groups.servers.databases.schemas. \ from pgadmin.browser.server_groups.servers.databases.schemas. \
fts_parser.tests import utils as fts_parser_utils fts_parsers.tests import utils as fts_parser_utils
from pgadmin.browser.server_groups.servers.databases.schemas.tests import \ from pgadmin.browser.server_groups.servers.databases.schemas.tests import \
utils as schema_utils utils as schema_utils
from pgadmin.browser.server_groups.servers.databases.schemas \ from pgadmin.browser.server_groups.servers.databases.schemas \

View File

@ -9,7 +9,7 @@
import uuid import uuid
from pgadmin.browser.server_groups.servers.databases.schemas.tables.column. \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.columns. \
tests import utils as columns_utils tests import utils as columns_utils
from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \
import utils as tables_utils import utils as tables_utils

View File

@ -10,7 +10,7 @@
import uuid import uuid
import json import json
from pgadmin.browser.server_groups.servers.databases.schemas.tables.column. \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.columns. \
tests import utils as columns_utils tests import utils as columns_utils
from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \
import utils as tables_utils import utils as tables_utils

View File

@ -9,7 +9,7 @@
import uuid import uuid
from pgadmin.browser.server_groups.servers.databases.schemas.tables.column. \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.columns. \
tests import utils as columns_utils tests import utils as columns_utils
from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \
import utils as tables_utils import utils as tables_utils

View File

@ -10,7 +10,7 @@
import json import json
import uuid import uuid
from pgadmin.browser.server_groups.servers.databases.schemas.tables.column. \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.columns. \
tests import utils as columns_utils tests import utils as columns_utils
from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.tests \
import utils as tables_utils import utils as tables_utils

View File

@ -1,11 +1,11 @@
""" """
We will use the exisiting modules for creating children module under We will use the existing modules for creating children module under
materialize views. materialize views.
Do not remove these imports as they will be automatically imported by the view Do not remove these imports as they will be automatically imported by the view
module as its children module as its children
""" """
from pgadmin.browser.server_groups.servers.databases.schemas.tables.column \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.columns \
import blueprint as columns_module import blueprint as columns_module
from pgadmin.browser.server_groups.servers.databases.schemas.tables.indexes \ from pgadmin.browser.server_groups.servers.databases.schemas.tables.indexes \
import blueprint as indexes_modules import blueprint as indexes_modules