Fusion 4.4.0 => 4.4.5

Just in case this affects anyone else.

I upgraded one of my test boxes today from 4.4.0 to 4.4.5, it all went smoothly apart from the upgrade schema in the GUI. It made changes to v_ring_groups and v_xml_cdr. With v_xml_cdr the upgrade tried to both add a new column and rename an old column to the name of the newly added one:
SQL:
ALTER TABLE v_xml_cdr ADD xml_cdr_uuid uuid;
ALTER TABLE v_xml_cdr RENAME COLUMN uuid to xml_cdr_uuid;
The rename fails so, in Adminer, I had to manually delete column xml_cdr_uuid and then rename uuid to xml_cdr_uuid.

Adrian.
 
@ElecBoy Glad you have solved it. For information, the section in my pg_hba.conf looks like this:
Code:
#Database administrative login by Unix domain socket
# TYPE  DATABASE        USER            ADDRESS                 METHOD
# "local" is for Unix domain socket connections only
local   all             postgres                                peer
# "local" is for Unix domain socket connections only
local   all             all                                     peer
# IPv4 local connections:
host    all             all             127.0.0.1/32            md5
# IPv6 local connections:
host    all             all             ::1/128                 md5
The other thing I was going to suggest was in Advanced -> Defaults, under Adminer, there is an option to set auto_login to true. then (after logging out and back in again to refresh the session) Advanced -> Adminer takes you straight in.