You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It shows up when you type \d+ in psql and a few other places and is a pretty nice way of documenting your database with the database.
It would be nice if these comments could be used to populate the avro doc fields. It will obviously be quite hard to figure out column descriptions if you run dbeam with --sqlFile, but if you run with --table it should be easier. This code could always try to probe the database for comments or only be activated by a flag.
If I have time later, I will try to add a pull-request, just wanted to first post my idea/feature request.
The text was updated successfully, but these errors were encountered:
Thanks for pointing to this (unknown for me) SQL concept.
dbeam currently gets all metadata information about an SQL table using interface ResultSetMetaData.
Using anything else (e.g. external utility psql) would make code much more complicated and vendor-specific.
Postgres has a non-standard SQL concept called comment:
https://www.postgresql.org/docs/current/sql-comment.html
It shows up when you type
\d+
inpsql
and a few other places and is a pretty nice way of documenting your database with the database.It would be nice if these comments could be used to populate the avro doc fields. It will obviously be quite hard to figure out column descriptions if you run dbeam with
--sqlFile
, but if you run with--table
it should be easier. This code could always try to probe the database for comments or only be activated by a flag.If I have time later, I will try to add a pull-request, just wanted to first post my idea/feature request.
The text was updated successfully, but these errors were encountered: