Pawel Sztromwasser wrote: > I investigated a bit and found out that this index in fact exists. I > managed to drop it manually using psql with command: > > DROP INDEX "dynamic"."D21886Filtercolumn" > > Command without schema name prefix (DROP INDEX "D21886Filtercolumn") > doesn't work. I checked the index dropping code and I found out that in > net.sf.basedb.core.dbengine.PostgresDbEngine.getDropIndexSql() method > code(line 120) creating 'drop index query' uses only index name without > schema name prefix. That is why an exception is thrown. > I didn't find anything about adding dynamic schema to users search_path > in PostgreSql in Base2 requirements. Some of the code in the same > 'problem causing' method adds schema prefix when dropping constraints, > so I consider this issue as a bug.
I think you are correct. The documentation for the method clearly mentions that it should generate SQL with the schema name included, but it doesn't. We'll fix it as soon as possible. The dropping of indexes is an important fix for performance but it doesn't affect the BASE application in any other way. With BASE 2.4.5 you will at least not get any more unwanted indexes on new experiments. /Nicklas ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ basedb-devel mailing list basedb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/basedb-devel
