Suggested advisory:
========================

The updated packages corrects many bugs and add many improvements, for instance, support for PostgreSQL 9.6.

========================

Packages in core/updates_testing:
========================
pgmodeler-0.9.0-1.mga6
pgmodeler-devel-0.9.0-1.mga6

from SRPM:
pgmodeler-0.9.0-1.mga6.src.rpm

Assignee: nicolas.salguero => qa-bugs
Status: NEW => ASSIGNED
Source RPM: (none) => pgmodeler-0.8.2-1.mga6.src.rpm

mga6  x86_64

Installed postgresql9.6 before updating pgmodeler.
Clean install.
pgmodeler opened up a full-window display onto which a number of example databases could be loaded via the Welcome page.  Tried pagila and the 3Dcity database which are kept at /usr/share/pgmodeler/samples/.  Various configuration files are created at ~/.config/pgmodeler.

I have no background in database programming so left it well alone.  Tables are displayed as graphical objects which can be moved around with the mouse.  Connections are defined for the various combinations of 1 and many and clearly labelled as such with direction vectors.

Exporting the current database to userspace was simple enough so this system ended up with a copy of the 3Dcity example as 3DCityDB_v3.3.sql.  Switched to the Demo.db and tried to find a way to import the copied database but could not figure out how to start the client server (what is it called for instance?).

There is no onboard help as such but Support links to a forum on github.  Context sensitive help is available wherever a ? is displayed.

Someone with a better knowledge of database culture is needed to test this fully but it looks like the gui works fine anyway.

CC: (none) => tarazed25

Poking this also for M6/64, but I believe Len's findings are good. The one thing I want to try is that an exported model can be imported into Postgres.
This good-looking application appears to be a one-man effort; and suffers from a total lack of documentation. It astonishes me that anyone can use it.

Already had PostgreSQL 9.6 installed:
 postgresql9.6-9.6.4-1.mga6
 postgresql9.6-server-9.6.4-1.mga6
 postgresql9.6-plpgsql-9.6.4-1.mga6
 postgresql-jdbc-9.4.1210-1.mga6

BEFORE update: pgmodeler-0.8.2-1.mga6.x86_64.rpm
Loaded the USDA example. Simply choosing the 'export' icon only offers PostgreSQL 9.5; enough said.

UPDATE to: pgmodeler-0.9.0-1.mga6
To continue later. Seems a good idea to install PHPpgsql first.

CC: (none) => lewyssmith

[continued]
Read 'phppgadmin'; installed, but no joy!
 /usr/share/doc/phppgadmin/INSTALL
 http://phppgadmin.sourceforge.net/doku.php?id=faq
have important information about login security, involving also a Postgres file.
 /etc/phppgadmin/config.inc.php
 /var/lib/pgsql/data/pg_hba.conf

 http://localhost/phppgadmin -> 404.
 file:///var/www/phppgadmin/index.php ->
 file:///var/www/phppgadmin/login.php ->
pop up a Firefox dialogue asking what to do with it, suggesting 'builder'. OK *appears* to go nowhere, but eventually pops up an application window about "Your computer is missing flatpak-builder" and offers to install it. (It also shows the PHP script). Installing involved a lot of downloading, root password, but then the cycle repeated. Blocked by this strange behaviour, unknown application. To bug?
------------------
Abandon phppgadmin!   [no such problem under Mageia 5]
------------------
Starting a new comment for clarity.

[continued]
Sarting updated pgmodeler complained about a corrupt config file, offered to re-set it to default, accepted, OK.
Re-opened the sample USDA file, and exported it immediately. The export dialogue starts with 'Database server', and it had 'found 1 connection'. At this point, the 'export' button is disabled. Selecting in the combo box 'local-db' activates the button. PostgreSQL 9.6 was pre-selected, no choice. Update OK!
(There are 2 other export possibilities: SQL and Graphics files).

Clicking 'export' really did it, directly into Postgres. A string of sensible messages ? one per table ? ending in success.

To test this, the absence of phppgadmlin is awkward. Scratching around for some Posgres usage, the MediaWiki wiki helped. At this point, user=postgres, no password.

$ psql -U postgres
psql (9.6.4)
Type "help" for help.

 postgres=# help
       \? for help with psql commands
 postgres=# \?
 ... take your pick.
 postgres=# \l+     [list databases]
   Name    |  Owner   | Encoding | Collate | Ctype |   Access privileges   |  Si
ze   | Tablespace |                Description                 
-----------+----------+----------+---------+-------+-----------------------+----
-----+------------+--------------------------------------------
...
 usda      | postgres | UTF8     | C       | C     |                       | 742
3 kB | pg_default |
and there is the DB exported from pgmodeler. Not so easy to see its tables:
 postgres=# \dtS+
listed a lot of Postgres tables; only. So quit:
 postgres=# \q
Read the psql man page, and tried logging in to the specific DB:
 $ psql usda -U postgres
psql (9.6.4)
 usda=# \?
...
 usda=# \dtS+
this time showed again all Postgres's own tables, followed by:
 public     | data_src                | table | postgres | 8192 bytes | 
 public     | datsrcln                | table | postgres | 0 bytes    | 
 public     | deriv_cd                | table | postgres | 8192 bytes | 
 public     | fd_group                | table | postgres | 8192 bytes | 
 public     | food_des                | table | postgres | 8192 bytes | 
 public     | footnote                | table | postgres | 8192 bytes | 
 public     | nut_data                | table | postgres | 8192 bytes | 
 public     | nutr_def                | table | postgres | 8192 bytes | 
 public     | src_cd                  | table | postgres | 8192 bytes | 
 public     | weight                  | table | postgres | 8192 bytes |
which look like the sample DB tables.
 usda=# \q

This update is certainly as good as its predecessor. OKing & validating.
Advisory uploaded ex Comment 1.

Keywords: (none) => advisory, validated_update
Whiteboard: (none) => MGA6-64-OK
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

http://advisories.mageia.org/MGAA-2017-0080.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED