StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
8533244
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-12-16T11:02:30.703
FavoriteCount
0
LastActivityDate
2011-12-16T16:00:06.073
LastEditDate
2011-12-16T16:00:06.073
LastEditorUserId
939860
OwnerUserId
939860
ParentId
8532125
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Consider the following demo. Temporary table for testing: <pre><code>CREATE TEMP TABLE nr(id int, nr numeric); INSERT INTO nr VALUES (1,1),(2,12),(3,13),(4,134),(5,135), (6,136),(7,1362),(8,1363); </code></pre> Query: <pre><code>SELECT nr FROM nr WHERE '1362235' ~~ (nr::text || '%') ORDER BY length(nr::text) DESC LIMIT 1; </code></pre> Delivers the longest match as requested. Operating with strings (not numbers) simplifies the task. You can change the data type in your table or you can cast the values in the query like I did. If you need it to be fast, change the type to <code>text</code> and index <code>nr</code>. A search like that can utilize a plain btree index (default) and will be very fast. <pre><code>CREATE INDEX nr_nr_idx ON nr (nr); </code></pre> If your database locale is not 'C' or 'POSIX', use <a href="http://www.postgresql.org/docs/current/interactive/indexes-opclass.html" rel="nofollow"><code>text_pattern_ops</code></a> as @Gavin commented, or the <code>LIKE</code> operator (<code>~~</code>) cannot use it even for the start of the column, because sort order is locale-specific. <pre><code>CREATE INDEX nr_nr_idx ON nr (nr text_pattern_ops); </code></pre> If you need your table column to be a numeric type, there is another option. Use an <a href="http://www.postgresql.org/docs/current/interactive/indexes-expressional.html" rel="nofollow">index on an expression</a> like so: <pre><code>CREATE INDEX nr_nr_idx ON nr ((nr::text) text_pattern_ops); </code></pre> The above query can utilize an index such as this one, because the expression matches the index expression.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPostgres - Match as much as possible of beginning of search parameter
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USErwin Brandstetter
UserOwnerUserId
1. USErwin Brandstetter
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
CommentsPostId
1. COprobably worth doing CREATE INDEX nr_nr_idx ON nr(nr text_pattern_ops) if you have much data.
 singulars
 PostPostId
 PO
 UserUserId
 USGavin
2. CO@Gavin: Good point! I amended my answer.
 singulars
 PostPostId
 PO
 UserUserId
 USErwin Brandstetter

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.