Open snaidaGithub opened 1 year ago
+1 for this. There are two important value-adds here:
// number of employees at this organization
. But:.comment()
, I could table.reduce(...)
the whole thing into JSON Schema where OpenAI requires parameter descriptions. For now I'm just copy/pasting all the schemas. Obviously not critical, but a nice ergnomic.
+1 for this. There are two important value-adds here:
- DB admin side, seeing what a column is for. Either at the SQL level (viewing a schema via DataGrip or whatever); or the code-level, a new dev looking through the schemas trying to understand the data layer. We're facing this issue currently, and of course the solution is code-level comments
// number of employees at this organization
. But:- Dynamic usage. I'm working with GPT Functions for inserting data via Chat. If I had
.comment()
, I couldtable.reduce(...)
the whole thing into JSON Schema where OpenAI requires parameter descriptions. For now I'm just copy/pasting all the schemas.Obviously not critical, but a nice ergnomic.
+1 I want to add point 3
postgraphile v5
graphql implementation. Postgraphile v5 uses column and table level comments extensively for defining behaviours that are used by postgraphile runtime engine.Any updates on this??
I am very much looking forward to this feature,COMMENT
+1
+1
+1
Describe what you want
It would be great to add a comment on Tables, Columns .... So that you can describe the tables, columns in the drizzle-orm model and it's also in the database, e.g. a database admin also needs this info in the db.
Maybe like this: