1. Forum
  2. USENET
  3. comp.databases.ingres

  • GUI vs SQL

    From Rich Ford@richford990@gmail.com to comp.databases.ingres on Thu Jan 6 13:39:12 2022
    From Newsgroup: comp.databases.ingres

    Is there any consensus over using a tool like DBeaver or just using sql from the command line?
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Karl Schendel@schendel@kbcomputer.com to Ingres and related product discussion forum on Thu Jan 6 17:33:56 2022
    From Newsgroup: comp.databases.ingres


    On Jan 6, 2022, at 4:39 PM, Rich Ford <richford990@gmail.com> wrote:

    Is there any consensus over using a tool like DBeaver or just using sql from the command line?
    It's entirely personal preference. I'm a firmly committed old-fashioned command line
    guy myself. (sql, not even isql.) I imagine that those who are more used to the
    pointy clicky stuff would use a pointy clicky tool. In the end, it doesn't really matter as long as the tool works well with Ingres
    Karl
    --- Synchronet 3.21b-Linux NewsLink 1.2
  • From Roy Hann@specially@processed.almost.meat to comp.databases.ingres on Thu Jan 6 23:37:51 2022
    From Newsgroup: comp.databases.ingres

    Rich Ford wrote:

    Is there any consensus over using a tool like DBeaver or just using sql
    from the command line?

    I use 'em both. I definitely use sql more though.

    The main reason I use DBeaver is when I have to see entire rows that
    would fold in sql. That's only a slight convenience, not a knock-out
    punch. And because I need to use sql for scripting anyway I usually
    already have it running. Also sql starts up in a trice.

    The compelling argument for using sql is you can display query plans in
    it, which you can't in DBeaver. (I do wish Ingres would treat QEPs as a
    core feature instead of delivering them like stowaways hidden in the wheel-well, but...)

    Roy

    --- Synchronet 3.21b-Linux NewsLink 1.2