StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2776308
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-05-05T19:52:26.857
FavoriteCount
0
LastActivityDate
2013-07-19T17:43:24.893
LastEditDate
2013-07-19T17:43:24.893
LastEditorUserId
277304
OwnerUserId
277304
ParentId
2774406
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
To add to the other answer, the behaviour of Postresql about case-sentivity of identifiers (table names and column names) is : <ul> <li>If the name is not quoted, it is converted to lowercase. Otherwise, it's left untouched.</li> <li>Afterwards, a case sensitive match is attempted.</li> </ul> This applies not only for queries, but also for schema manipulation; in particular: table creation. <a href="http://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS" rel="noreferrer">The golden rule is consistency</a>: <blockquote> If you want to write portable applications you are advised to always quote a particular name or never quote it </blockquote> The posted problem arose, probably, because the tables and columns names were quoted at creation time (hence, they were not converted to lowercase). So, now they must be quoted (and case-sensitive) in all queries. Normally, all works as expected. <pre><code>db=# create table Xxx (id integer); -- unquoted, will be converted to lowercase CREATE TABLE db=# select * from xXx; -- this works ok id ---- (0 rows) db=# create table "Xxxx" (id integer); -- will be left untouched CREATE TABLE db=# select * from xxxx; -- bad ERROR: relation "xxxx" does not exist LINE 1: select * from xxxx; db=# select * from Xxxx; -- bad ERROR: relation "xxxx" does not exist LINE 1: select * from Xxxx; ^ db=# select * from "Xxxx"; -- ok id ---- (0 rows) db=# \dt *xx* List of relations Schema | Name | Type | Owner --------+------+-------+---------- public | Xxxx | table | postgres public | xxx | table | postgres </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPsycopg2 doesn't like table names that start with a lower case letter
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USleonbloy
UserOwnerUserId
1. USleonbloy
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO+1 for example and explanation.
 singulars
 PostPostId
 PO
 UserUserId
 USBurhan Khalid

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.