A new topic, 'Migration failing due to permission denied for relation I am not
even using', has been made on a board you are watching.
You can see it at
http://liquibase.org/forum/index.php?topic=134.new#new
The text of the topic is shown below:
Hi All,
I am very new with Liquibase and I am using Liquibase plug in for Grails and
when I try to execute the migration on an existing Postgresql database I am
getting the following exception:
org.postgresql.util.PSQLException: ERROR: permission denied for relation
lock_details
I am adding new tables, constraints, foreign keys, etc., but I am not changing
with existing tables and for what I am seeing in the Postgres log files, it
seems that Liquibase goes through all the tables doing selects like this:
SELECT id FROM public.comments WHERE 1 = 0
but when it gets to lock_details, it breaks because this is a view that belongs
to the postgres user, which is not the one I am using, and my user does not
have access to this view.
My biggest question here is why Liquibase needs to do this and how can I
prevent it from crashing when doing this kind of selects on table/views that my
user doesn't have access to?
Any help is very much appreciated!!
Thanks!!
Unsubscribe to new topics from this board by clicking here:
http://liquibase.org/forum/index.php?action=notifyboard;board=1.0
Regards,
The LiquiBase Community Forum Team.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Liquibase-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/liquibase-user