libgda issueshttps://gitlab.gnome.org/GNOME/libgda/-/issues2019-10-09T16:12:35Zhttps://gitlab.gnome.org/GNOME/libgda/-/issues/40Document GdaServerOperationNode and friends as for providers only?2019-10-09T16:12:35ZBugzillaDocument GdaServerOperationNode and friends as for providers only?## Submitted by Murray Cumming `@murrayc`
Assigned to **mal..@..db.org**
**[Link to original bug (#574742)](https://bugzilla.gnome.org/show_bug.cgi?id=574742)**
## Description
Maybe GdaServerOperationNode
and anything that uses G...## Submitted by Murray Cumming `@murrayc`
Assigned to **mal..@..db.org**
**[Link to original bug (#574742)](https://bugzilla.gnome.org/show_bug.cgi?id=574742)**
## Description
Maybe GdaServerOperationNode
and anything that uses GdaServerOperationNode* should be documented as only for use by provider implementations.
Version: 3.99.xGDA 7.0https://gitlab.gnome.org/GNOME/libgda/-/issues/39Document GdaSetSource as for providers only?2019-10-09T16:25:24ZBugzillaDocument GdaSetSource as for providers only?## Submitted by Murray Cumming `@murrayc`
Assigned to **mal..@..db.org**
**[Link to original bug (#574741)](https://bugzilla.gnome.org/show_bug.cgi?id=574741)**
## Description
I suspect that GdaSetSource
http://library.gnome.org/...## Submitted by Murray Cumming `@murrayc`
Assigned to **mal..@..db.org**
**[Link to original bug (#574741)](https://bugzilla.gnome.org/show_bug.cgi?id=574741)**
## Description
I suspect that GdaSetSource
http://library.gnome.org/devel/libgda/unstable/GdaSet.html#GdaSetSource
and functions that use it, such as
http://library.gnome.org/devel/libgda/unstable/GdaSet.html#gda-set-get-source-for-model
should be documented as only for use by providers or implementors of GdaDataModels.
Version: 3.99.xGDA 7.0https://gitlab.gnome.org/GNOME/libgda/-/issues/38gda_connection_open_from_string should create connections strings transparently2018-10-10T17:20:23ZBugzillagda_connection_open_from_string should create connections strings transparently## Submitted by Piotr Pokora
Assigned to **mal..@..db.org**
**[Link to original bug (#572393)](https://bugzilla.gnome.org/show_bug.cgi?id=572393)**
## Description
gda_connection_open_from_string is well documented, however it miss...## Submitted by Piotr Pokora
Assigned to **mal..@..db.org**
**[Link to original bug (#572393)](https://bugzilla.gnome.org/show_bug.cgi?id=572393)**
## Description
gda_connection_open_from_string is well documented, however it misses few important points: when using SQLite provider you have to pass DB_DIR key and TNSNAME one when you use Oracle provider. Also GDA3 expects 'USER' key while GDA4 expects 'USERNAME'. I expect any application which provides abstract database access based on GDA, "abuses" own code with many conditional control blocks which could be implemented (and encapsulated) by GDA itself.
Other information:
Version: 3.99.xGDA 7.0https://gitlab.gnome.org/GNOME/libgda/-/issues/36GRANT/REVOKE API2018-09-21T21:40:47ZBugzillaGRANT/REVOKE API## Submitted by Rodrigo Moya `@rodrigo`
Assigned to **mal..@..db.org**
**[Link to original bug (#82679)](https://bugzilla.gnome.org/show_bug.cgi?id=82679)**
## Description
We need a API for clients to be able to GRANT/REVOKE right...## Submitted by Rodrigo Moya `@rodrigo`
Assigned to **mal..@..db.org**
**[Link to original bug (#82679)](https://bugzilla.gnome.org/show_bug.cgi?id=82679)**
## Description
We need a API for clients to be able to GRANT/REVOKE rights on DB objects.
This API should be flexible enough for managing as many scenarios as possible.
So far, here are the thoughts:
> >
> > > - we need to allow the application to know what options the provider
> > > accepts to adapt the GUI to what is available only
> > >
> > ok, that is perfectly doable. What are the options you're thinking
> > about?
>
> Several options:
> - types of rights (read, insert, update, or read, write, etc);
> - if rights are managed at the level of a database, a table or some
> columns of a table, sequence, index, vues...
> - the kind of rights for a user (create DBs, create other users, change
> passwords of other users, etc).
> - maybe other ones.
>
Version: 0.8.xGDA 7.0https://gitlab.gnome.org/GNOME/libgda/-/issues/34Rule support2018-09-21T21:42:33ZBugzillaRule support## Submitted by Jean-Michel POURE
Assigned to **mal..@..db.org**
**[Link to original bug (#71089)](https://bugzilla.gnome.org/show_bug.cgi?id=71089)**
## Description
Libgda should support Rules, which are modifiers that change SQL...## Submitted by Jean-Michel POURE
Assigned to **mal..@..db.org**
**[Link to original bug (#71089)](https://bugzilla.gnome.org/show_bug.cgi?id=71089)**
## Description
Libgda should support Rules, which are modifiers that change SQL queries
server-side, on the fly.
For example, in PostgreSQL, rules can be used to update views (when an SQL
update query on a view is parsed, it is rewritten to update the parent table).GDA 7.0https://gitlab.gnome.org/GNOME/libgda/-/issues/33PostgreSQL CREATE OR REPLACE FUNCTION, VIEW, TRIGGER2018-09-21T21:44:13ZBugzillaPostgreSQL CREATE OR REPLACE FUNCTION, VIEW, TRIGGER## Submitted by Jean-Michel POURE
Assigned to **mal..@..db.org**
**[Link to original bug (#71087)](https://bugzilla.gnome.org/show_bug.cgi?id=71087)**
## Description
Since 7.2, PostgreSQL supports CREATE OR REPLACE FUNCTION to all...## Submitted by Jean-Michel POURE
Assigned to **mal..@..db.org**
**[Link to original bug (#71087)](https://bugzilla.gnome.org/show_bug.cgi?id=71087)**
## Description
Since 7.2, PostgreSQL supports CREATE OR REPLACE FUNCTION to allows
function edition. PostgreSQL does not support CREATE OR REPLACE VIEW OR
CREATE OR REPLACE TRIGGER which will only be added in 7.3.
Therefore, modifying a view or a trigger is tedious and boring : you need
to drop it before recreating it. If the new definition is mistaken, you
loose the view/trigger.
Using libgda it should be possible to virtually modify a view or a trigger
using DROP/CREATE in a single transaction.GDA 7.0