Search Postgresql Archives

composite type vs table

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
I'm using composite types within my database and I sometimes need to modify type either by adding new column or e.g. renaming a column. Of course I can't do that on existing composite type (actually I can, but that is quite complicated) so maybe I should use table instead ? With tables (that are composite types too) I can do many operations, that are not available for composite type. I would like to ask, whether there are any disadvantages (e.g. performance) of using tables instead composite types (comparing only those functionality that is available for composite types) ?

Regards,
ML



---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
      message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux