Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • L libgda
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 65
    • Issues 65
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • libgda
  • Issues
  • #238

Closed
Open
Created Nov 14, 2020 by Danilo Galete@galetedanilo💬Contributor

Centralizing features for GdaConnection

I would like to present a brief idea for a possible way of using Libgda.

1 - The connection class is an object only for connection and connection information to the database. For example, SSL, TLS connections, among other ways. It is also possible through this class to obtain connection information. 2 - Create classes for DML commands. 3 - Create classes for DDL commands

For example methods like: gda_connection_delete_row_from_table

We would have something like: gda_dml_delete_row

This is just an idea, a decentralization of gda connection, transferring functionality to other classes specific to a particular operation.

Edited Nov 15, 2020 by Danilo Galete
Assignee
Assign to
Time tracking