Re: Noob question: Making search results clickable.
| From: | Nathan Rixham | Date: | Fri, 20 Nov 2009 09:37:15 +0000 |
| Subject: | Re: Noob question: Making search results clickable. | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-299955@lists.php.net to get a copy of this message | ||
Ford, Mike wrote:
>> -----Original Message-----
>> From: Nisse Engström [mailto:news.NOSPAM.0ixbtqKe@luden.se]
>> Sent: 19 November 2009 14:54
>> To: php-general@lists.php.net
>> Subject: Re: [PHP] Noob question: Making search results clickable.
>>
>> On Wed, 18 Nov 2009 10:31:59 -0500, Paul M Foster wrote:
>>
>>> Replace your query with:
>>>
>>> "SELECT title, id FROM videos WHERE topid1 = '$topic'"
>>>
>>> or whatever index you have to select a particular video from your
>> table.
>>> Replace your echo statement above with:
>>>
>>> echo "<a
>> href="video_display.php?video_id=$row[id]">$row[title]</a>";
>>
>> Without actually checking, I don't think "$row[...]"
>> is going to work in double quoted strings. I'm pretty
>> sure it needs to be in braces. You also need to escape
>> the double quotes and put the array indexes in single
>> quotes:
>
> You should have checked, because "...$row[title]..." is a valid alternative for
> "...{$row['title']}...".
>
> Personally, I never use it because of it not having the same meaning outside a double-quoted
> string -- but it is a documented feature.
>
yup, which sucks and breaks at the drop of a hat, like..
<?php
$a = array();
$a['val id'] = 123;
echo "something $a[val id] and more";
produces: parse error, expecting `']''
best avoided imho