Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 6
Impact
~4k people reached

  • 0 posts edited
  • 0 helpful flags
  • 7 votes cast
Apr
29
awarded  Notable Question
Jul
30
awarded  Popular Question
Apr
2
awarded  Commentator
Mar
20
accepted PostgresSQL: Get single attribute of UDT in SELECT statement
Mar
20
comment PostgresSQL: Get single attribute of UDT in SELECT statement
Thanks! The difference is very subtle. Btw, I thought it might be somewhere written in the manual, but I really couldn't find it. Thanks again!
Mar
20
awarded  Editor
Mar
20
revised PostgresSQL: Get single attribute of UDT in SELECT statement
deleted 3 characters in body; added 76 characters in body; edited title
Mar
20
asked PostgresSQL: Get single attribute of UDT in SELECT statement
Feb
28
answered Postgresql: type_modifier in UDT
Feb
27
comment Display user-defined types and their details
Thanks a lot for the code and the explanations. Just one thing: what do you mean by ´\d...´ commands?
Feb
27
awarded  Supporter
Feb
27
accepted Display user-defined types and their details
Feb
26
asked Display user-defined types and their details
Feb
26
comment Postgresql: type_modifier in UDT
Makes very much sense! Thanks for this very good explanation!
Feb
26
accepted Postgresql: type_modifier in UDT
Feb
26
comment Postgresql: type_modifier in UDT
Sorry for being unclear! Yes, I was thinking of a trigger; but is it possible that the name of the trigger is specified with the data declaration? E.g. assume there are multiple triggers (t1, t2,...), and a udt (my_udt): is it possible that at the time of creation of the table the user specifies ´CREATE TABLE test ( attribute my_udt t1)´ and a function in my_udt interprets that t1 as being the name of a trigger to be added?
Feb
26
asked Postgresql: type_modifier in UDT
Jan
31
comment Use GIN to index bit strings
Thanks a lot for this detailed answer! That's great!
Jan
31
awarded  Scholar
Jan
31
accepted Use GIN to index bit strings