Postgres Pro
Downloads
Home   >   mailing lists

Thread: [pgAdmin III] #91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0

[pgAdmin III] #91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0

From
"pgAdmin Trac"
Date:
#91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0
-----------------------------------+----------------------------------------
 Reporter:  Jean-Pierre Pelletier  |       Owner:  dpage 
     Type:  bug                    |      Status:  new   
 Priority:  minor                  |   Milestone:  1.10.1
Component:  pgadmin                |     Version:  1.10  
 Keywords:  textsearch             |    Platform:  all   
-----------------------------------+----------------------------------------
 We've noticed that pgAdmin displays the mapping of text search
 configurations out of order
 after using pg_dump & pg_restore with pgAdmin 1.10.0 against PostgreSQL
 8.3.8 on Windows Server 2008 64 bits.

 Thanks,
 Jean-Pierre Pelletier

 Steps to reproduce:

 CREATE SCHEMA my_text_search_configuration;
 CREATE TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english (
   PARSER = "default"
 );
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR asciihword
 WITH english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR asciiword
 WITH english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR email WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR file WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR float WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR host WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR hword WITH
 english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR
 hword_asciipart WITH english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR
 hword_numpart WITH simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR hword_part
 WITH english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR int WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR numhword
 WITH simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR numword
 WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR sfloat
 WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR uint WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR url WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR url_path
 WITH simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR version
 WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR word WITH
 english_stem,simple;

 pg_dump --schema my_text_search_configuration

 -- move schema out of the way to restore in same database
 ALTER SCHEMA my_text_search_configuration RENAME TO
 my_text_search_configuration_old;

 pg_restore

 psql properly displays the configuration

 \dF+ my_text_search_configuration.mytsconfig_english
 Text search configuration
 "my_text_search_configuration.mytsconfig_english"
 Parser: "pg_catalog.default"
       Token      |    Dictionaries
 -----------------+---------------------
  asciihword      | english_stem,simple
  asciiword       | english_stem,simple
  email           | simple
  file            | simple
  float           | simple
  host            | simple
  hword           | english_stem,simple
  hword_asciipart | english_stem,simple
  hword_numpart   | simple
  hword_part      | english_stem,simple
  int             | simple
  numhword        | simple
  numword         | simple
  sfloat          | simple
  uint            | simple
  url             | simple
  url_path        | simple
  version         | simple
  word            | english_stem,simple

 but after the restore, pgAdmin displays the following:

 CREATE TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english (
   PARSER = "default"
 );
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR asciihword
 WITH simple,english_stem;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR asciiword
 WITH english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR email WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR file WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR float WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR host WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR hword WITH
 english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR
 hword_asciipart WITH english_stem,simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR
 hword_numpart WITH simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR hword_part
 WITH simple,english_stem;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR int WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR numhword
 WITH simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR numword
 WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR sfloat
 WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR uint WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR url WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR url_path
 WITH simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR version
 WITH
 simple;
 ALTER TEXT SEARCH CONFIGURATION
 my_text_search_configuration.mytsconfig_english ADD MAPPING FOR word WITH
 simple,english_stem;

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/91>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

Re: [pgAdmin III] #91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0

From
"pgAdmin Trac"
Date:
#91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0
-----------------------------------+----------------------------------------
 Reporter:  Jean-Pierre Pelletier  |       Owner:  gleu    
     Type:  bug                    |      Status:  assigned
 Priority:  minor                  |   Milestone:  1.10.1  
Component:  pgadmin                |     Version:  1.10    
 Keywords:  textsearch             |    Platform:  all     
-----------------------------------+----------------------------------------
Changes (by gleu):

  * owner:  dpage => gleu
  * status:  new => assigned


--
Ticket URL: <http://code.pgadmin.org/trac/ticket/91#comment:1>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

Re: [pgAdmin III] #91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0

From
"pgAdmin Trac"
Date:
#91: Text Search Configuration Mapping displayed out of order, pgAdmin 1.10.0
------------------------------------+---------------------------------------
  Reporter:  Jean-Pierre Pelletier  |       Owner:  gleu      
      Type:  bug                    |      Status:  closed    
  Priority:  minor                  |   Milestone:  1.10.1    
 Component:  pgadmin                |     Version:  1.10      
Resolution:  fixed                  |    Keywords:  textsearch
  Platform:  all                    |  
------------------------------------+---------------------------------------
Changes (by gleu):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 Fixed in r8078 and r8079.

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/91#comment:2>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III