On Thu, Mar 12, 2020 at 1:36 PM ivanmarcus <ivanmar...@yahoo.com> wrote:

> Mike,
>
> I was about to try transferring a running 1.0.0 I have to a new 1.1.0
> instance so I could confirm the process I'd suggested earlier. Out of
> interested I checked out the database tables first.
>
> Here's 1.0.0:
>
> +---------------------------------------+
> | Tables_in_guacamole_db                |
> +---------------------------------------+
> | guacamole_connection                  |
> | guacamole_connection_group            |
> | guacamole_connection_group_permission |
> | guacamole_connection_history          |
> | guacamole_connection_parameter        |
> | guacamole_connection_permission       |
> ...
>
> 14 rows in set
>

This is not a 1.0.0 database. You're missing the guacamole_entity table,
guacamole_user_group table, etc. which were added in 1.0.0 as part of
adding group support. See the changes applied by the
"upgrade-pre-1.0.0.sql" script:

https://github.com/apache/guacamole-client/blob/3b97349f055b064c8994c7a2ac3f0cfd6ed39e27/extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-mysql/schema/upgrade/upgrade-pre-1.0.0.sql

And the relevant section of the compatibility notes for the 1.0.0 release:

http://guacamole.apache.org/releases/1.0.0/#database-schema-changes

Then in 1.1.0 I find:
>
> +---------------------------------------+
> | Tables_in_guacamole_db                |
> +---------------------------------------+
> | guacamole_connection                  |
> | guacamole_connection_attribute        |
> | guacamole_connection_group            |
> | guacamole_connection_group_attribute  |
> | guacamole_connection_group_permission |
> | guacamole_connection_history          |
> | guacamole_connection_parameter        |
> | guacamole_connection_permission       |
> | guacamole_entity                      |
> ...
> 23 rows in set
>

This is the correct schema for 1.0.0 and forward, including 1.1.0. There
have been no changes to the schema since 1.0.0:

[mjumper@dev-mjumper guacamole-client]$ git diff --stat 0.9.14..1.0.0
extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-mysql/schema/001-create-schema.sql
 .../schema/001-create-schema.sql                   | 284
++++++++++++++++++---
 1 file changed, 248 insertions(+), 36 deletions(-)
[mjumper@dev-mjumper guacamole-client]$ git diff --stat 1.0.0..1.1.0
extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-mysql/schema/001-create-schema.sql
[mjumper@dev-mjumper guacamole-client]$ git diff --stat
1.1.0..staging/1.2.0
extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-mysql/schema/001-create-schema.sql
[mjumper@dev-mjumper guacamole-client]$

The 1.0.0 instance has been running fine since a few days after release and
> was an upgrade from 0.9.14. Not sure if that makes a difference or not but
> I would have thought from the above that one would need to run the script
> to create the new tables etc for 1.1.0?
>

There are no new tables for 1.1.0. There were new tables for 1.0.0, which
would be created if you run the "upgrade-pre-1.0.0.sql" script. I'm not
sure why the older 0.9.14 database would be working with 1.0.0 or onward,
but my guess would be that it isn't, and that if it's not failing with
blatant errors it may be failing in other more subtle ways. It's definitely
the wrong schema.

- Mike

Reply via email to