StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13727954
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-05T16:35:45.467
FavoriteCount
0
LastActivityDate
2012-12-06T17:13:57.100
LastEditDate
2012-12-06T17:13:57.100
LastEditorUserId
68623
OwnerUserId
68623
ParentId
13726515
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
If you are willing to break your <code>INSERT</code> statements into one row of data per insert, then you could use <a href="http://www.postgresql.org/docs/9.1/static/rules-update.html" rel="nofollow">PostgreSQL rules</a>. The example that follows is a bit convoluted in that rules don't seem to let you redirect writes to a relation itself. That's usually done with triggers. But we're seeing if this is possible without triggers, so here goes: <pre><code>--drop table table_data cascade; CREATE TABLE table_data ( month integer not null, task integer not null, "desc" text ); ALTER TABLE table_data add primary key (month, task); CREATE VIEW "table" as select month, task, "desc" from table_data; CREATE OR REPLACE RULE calculate_task AS ON INSERT TO "table" DO INSTEAD INSERT into table_data (month, task, "desc") VALUES ( NEW.month, (select coalesce(max(task),0) + 1 from table_data where month = NEW.month), NEW."desc"); BEGIN; INSERT INTO "table" ("month", "desc") VALUES (1, 'One thing'); INSERT INTO "table" ("month", "desc") VALUES (1, 'Another thing'); INSERT INTO "table" ("month", "desc") VALUES (1, 'Last task of the month'); INSERT INTO "table" ("month", "desc") VALUES (2, 'Last task of the month'); INSERT INTO "table" ("month", "desc") VALUES (2, 'Last task of the month'); INSERT INTO "table" ("month", "desc") VALUES (3, 'First of third month'); COMMIT; select * from "table"; </code></pre> Notes <ul> <li>If you need to support DELETE/UPDATE on "table", then you could add rules for each those actions as well.</li> <li>The <code>BEGIN</code> and <code>COMMIT</code> block above is used to show that even within the same transaction, this method will work as long as each row is broken into its own <code>INSERT</code>.</li> <li>You use a few <a href="http://www.postgresql.org/docs/9.1/static/sql-keywords-appendix.html" rel="nofollow">reserved words</a> like <code>table</code> and <code>desc</code>. Be sure to double-quote them as you've done and you won't have any problems.</li> </ul> <a href="http://sqlfiddle.com/#!12/98e10/2" rel="nofollow">Here</a> is the above code in sqlfiddle
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIncrementing multi-column sequence in PostgreSQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJoshua Berry
UserOwnerUserId
1. USJoshua Berry
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.