Discussion for users on SQL related matters.
| Thread | Author | Time |
|---|---|---|
| NORM(NO ORM) transform two one-many relationships into a single json. 📎 | Jian He | 13:58 |
| Global setting for ORDER BY ... NULLS FIRST / LAST | Sebastien Flaesch | 14:16 |
| Re: Global setting for ORDER BY ... NULLS FIRST / LAST | David G. Johnston | 14:41 |
| Re: Global setting for ORDER BY ... NULLS FIRST / LAST | Tom Lane | 15:02 |
| pg_stat_progress_copy not working as intended | asalias mark | 17:55 |
| Thread | Author | Time |
|---|---|---|
| Re: pg_stat_progress_copy not working as intended | Ian Lawrence Barwick | 00:17 |
| Re: pg_stat_progress_copy not working as intended | asalias mark | 09:48 |
| Re: Global setting for ORDER BY ... NULLS FIRST / LAST | Sebastien Flaesch | 12:23 |
| Thread | Author | Time |
|---|---|---|
| Bug in tables column data in postgres database | Sarita Sharma | 16:45 |
| AW: Bug in tables column data in postgres database | 17:10 | |
| Re: Bug in tables column data in postgres database | Christophe Pettus | 17:18 |
| Re: Bug in tables column data in postgres database 📎 | MichaelDBA Vitale | 17:24 |
| RE: Bug in tables column data in postgres database | Voillequin, Jean-Marc | 18:06 |
| Re: Bug in tables column data in postgres database | Sarita Sharma | 18:41 |
| Re: Bug in tables column data in postgres database | Rob Sargent | 19:24 |
| Re: Bug in tables column data in postgres database | David G. Johnston | 19:27 |
| Re: Bug in tables column data in postgres database | Steve Midgley | 20:03 |
| Thread | Author | Time |
|---|---|---|
| Re: Bug in tables column data in postgres database | Sarita Sharma | 08:04 |
| Re: Bug in tables column data in postgres database | David G. Johnston | 08:15 |
| Re: Bug in tables column data in postgres database | Sarita Sharma | 08:29 |
| Re: Bug in tables column data in postgres database | Thomas Kellerer | 08:40 |
| Re: Bug in tables column data in postgres database | David G. Johnston | 08:51 |
| Re: Bug in tables column data in postgres database | mgbii bax | 10:10 |
| Re: Bug in tables column data in postgres database | Sarita Sharma | 10:28 |
| Re: Bug in tables column data in postgres database | David G. Johnston | 15:27 |
| Re: Bug in tables column data in postgres database | Sarita Sharma | 15:56 |
| Re: Bug in tables column data in postgres database | David G. Johnston | 16:07 |
| Thread | Author | Time |
|---|---|---|
| Re: Bug in tables column data in postgres database | Sándor Daku | 10:08 |
| Re: Bug in tables column data in postgres database | Michaeldba@sqlexec.com | 12:23 |
| Re: Bug in tables column data in postgres database | Sarita Sharma | 13:49 |
| Thread | Author | Time |
|---|---|---|
| ERROR: extra data after last expected column | Scott Macri | 01:59 |
| Re: ERROR: extra data after last expected column | Sándor Daku | 09:08 |
| Re: ERROR: extra data after last expected column | Rob Sargent | 09:57 |
| Best practice for naming temp table trigger functions | Sebastien Flaesch | 18:19 |
| Re: ERROR: extra data after last expected column | scott macri | 23:33 |
| Re: ERROR: extra data after last expected column | Steve Midgley | 23:54 |
| Re: ERROR: extra data after last expected column | Steve Midgley | 23:56 |
| Re: ERROR: extra data after last expected column | Rob Sargent | 23:57 |
| Thread | Author | Time |
|---|---|---|
| Re: ERROR: extra data after last expected column | Scott Macri | 01:40 |
| Re: ERROR: extra data after last expected column | Ron | 01:42 |
| Re: ERROR: extra data after last expected column | Scott Macri | 01:51 |
| Re: ERROR: extra data after last expected column | Rob Sargent | 02:40 |
| Re: ERROR: extra data after last expected column | scott macri | 03:47 |
| Re: Best practice for naming temp table trigger functions | Sebastien Flaesch | 15:38 |
| Re: Best practice for naming temp table trigger functions | David G. Johnston | 16:16 |
| RE: unique index with several columns | Voillequin, Jean-Marc | 16:59 |
| Re: Best practice for naming temp table trigger functions | Sebastien Flaesch | 17:24 |
| Thread | Author | Time |
|---|---|---|
| Re: Best practice for naming temp table trigger functions | Sebastien Flaesch | 08:26 |
| Thread | Author | Time |
|---|---|---|
| Apparently table locks are the key issue to see red flags | Shaozhong SHI | 20:14 |
| Apparently table locks are the key issue to see red flags | Shaozhong SHI | 20:15 |
| Re: Apparently table locks are the key issue to see red flags | Ron | 20:21 |
| Re: Apparently table locks are the key issue to see red flags | Adrian Klaver | 20:23 |
| How to explicitly lock and unlock tables in pgsql? | Shaozhong SHI | 20:30 |
| How to explicitly lock and unlock tables in pgsql? | Shaozhong SHI | 20:30 |
| Apparently table locks are the key issue to see red flags | Shaozhong SHI | 20:32 |
| Re: How to explicitly lock and unlock tables in pgsql? | Fabrízio de Royes Mello | 20:35 |
| How to explicitly state unlock in sql? | Shaozhong SHI | 20:56 |
| Re: How to explicitly state unlock in sql? | Rob Sargent | 21:03 |
| Re: How to explicitly state unlock in sql? | Tom Lane | 21:06 |
| Thread | Author | Time |
|---|---|---|
| Re: How to explicitly lock and unlock tables in pgsql? | Laurenz Albe | 07:51 |
| Re: Apparently table locks are the key issue to see red flags | Jayson Hreczuck | 13:21 |
| Thread | Author | Time |
|---|---|---|
| PostgreSQL trigger on user logon | Kevin Tu | 14:46 |
| Re: How to explicitly lock and unlock tables in pgsql? | Merlin Moncure | 16:38 |
| Re: PostgreSQL trigger on user logon | Steve Midgley | 19:58 |
| Re: How to explicitly lock and unlock tables in pgsql? | Laurenz Albe | 22:48 |
| Thread | Author | Time |
|---|---|---|
| the order of operator computation | Jian He | 04:46 |
| Re: the order of operator computation | Tom Lane | 05:32 |