StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6316996
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-06-11T16:08:55.377
FavoriteCount
0
LastActivityDate
2011-06-11T18:41:34.613
LastEditDate
2011-06-11T18:41:34.613
LastEditorUserId
560648
OwnerUserId
560648
ParentId
6316851
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
If <code>ids</code> is a field containing comma-delimited values, then your query is like: <pre><code>SELECT * FROM `informations` WHERE 3 IN ("1,2,3,4,5") </code></pre> Instead of what it should be: <pre><code>SELECT * FROM `informations` WHERE 3 IN (1,2,3,4,5) </code></pre> There is no automatic tokenisation (splitting on <code>,</code>) performed; the one value of <code>ids</code> is not automatically converted into a list for you such that <code>IN</code> can work. Unfortunately your table design has been your undoing here. Can you split the IDs into a separate table using the principle of database normalisation? Then your query might look like: <pre><code>SELECT * FROM `informations` WHERE 3 IN ( SELECT `id` FROM `ids` WHERE `informations`.`id` = `ids`.`information_id` ) </code></pre> BTW, "information" is a non-countable noun and, as such, "informations" is wrong. <hr> Update (thanks for the idea, a1ex07!) Although this is hackery and I still suggest fixing your table layout, I'll be kind and suggest a quick fix. Willempie was close with: <pre><code>$query = 'SELECT * FROM `informations` WHERE `ids` LIKE "%' . $id . '%"'; </code></pre> Unfortunately, a wildcard match isn't quite powerful enough. Consider if <code>ids</code> is like <code>"1,6,9,12,35,4"</code> and <code>$id</code> is like <code>3</code>. You get a false positive. The <code>LIKE</code> statement needs to be aware of the commas. You can add multiple cases: <pre><code>$query = 'SELECT * FROM `informations` WHERE `ids` LIKE "%,' . $id . ',%" OR `ids` LIKE "%,' . $id . '" OR `ids` LIKE "' . $id . ',%"'; </code></pre> Or, for brevity, you can work around this with <a href="http://dev.mysql.com/doc/refman/5.1/en/regexp.html#operator_regexp" rel="nofollow">regular expressions</a>: <pre><code>$query = 'SELECT * FROM `informations` WHERE `ids` REGEXP "(^|,)' . $id . '(,|$)"'; </code></pre> For any <code>$id</code> you wish to find, before it must be the start of <code>ids</code> (<code>^</code>) or a comma; after it must be a comma or the end of <code>ids</code> (<code>$</code>). This ensures that <code>$id</code> must be found as a whole, comma-delimited token. It's a little like "Whole Word Only" in word processor searches, but with commas separating "words" instead of spaces. <hr> Update 2 Another way uses <a href="http://dev.mysql.com/doc/refman/5.0/en/string-functions.html#function_find-in-set" rel="nofollow"><code>FIND_IN_SET</code></a>, which performs a search within a comma-delimited string: <pre><code>$query = 'SELECT * FROM `informations` WHERE FIND_IN_SET("' . $id . '", `ids`)'; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWHERE IN SQL condition problem
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USLightness Races in Orbit
UserOwnerUserId
1. USLightness Races in Orbit
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWHERE IN SQL condition problem
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
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.