Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #15794

Re: rawurlencode problem

Show all headers | View raw

Arno Welzel schrieb am 2015-10-27 um 14:01:

> J.O. Aho schrieb am 2015-10-20 um 07:10:
> 
>> On 10/19/2015 09:43 PM, Derek Turner wrote:
>>> On Mon, 19 Oct 2015 21:27:54 +0200, J.O. Aho wrote:
>>>
>>>> The standard is to use a numeric id in the database, it's a lot easier
>>>> to validate that it seems to be okey and numeric index in the database
>>>> is faster than varchar/text based.
>>>>
>>>> I would recommend a redesign of your database and it will solve your
>>>> problem too.
>>>
>>> I really don't see how that even begins to answer my question. There is, 
>>> of course, an auto-incrementing integer primary key in all four tables. 
>>
>> That wasn't in your example and your use of the "name" gave the
>> impression your database could be flawed.
> 
> The name was used to create a link to another section *within* the same
> document:
> 
> <a href="#SomeName">Some Name</a>
> 
> <h2 id="SomeName">Some Name</h2>
> 
> 
> I would also advise to use the numerical IDs from the database for this
> purpose and use title attributes in the links for the description:
> 
> <a href="#1" title="Some Name">Some Name</a>
> 
> 
> <h2 id="1">Some Name</h2>

Of course not "1" but "l1" or similar (starting with an alpha character
since numbers are not valid as IDs.

> The title can be created using htmlspecialchars()
> 
> Also see here:
> 
> <http://www.w3.org/TR/WCAG20-TECHS/H33.html>


-- 
Arno Welzel
http://arnowelzel.de
http://de-rec-fahrrad.de
http://fahrradzukunft.de

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

rawurlencode problem Derek Turner <frderek@suremail.je> - 2015-10-19 14:56 +0000
  Re: rawurlencode problem Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-10-19 17:18 +0200
    Re: rawurlencode problem Derek Turner <frderek@suremail.je> - 2015-10-19 15:48 +0000
      Re: rawurlencode problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-20 00:02 +0200
        Re: rawurlencode problem Erwin Moller <erwinmollerusenet@xs4all.nl> - 2015-10-21 09:40 +0200
    Re: rawurlencode problem "J.O. Aho" <user@example.net> - 2015-10-20 18:33 +0200
  Re: rawurlencode problem "J.O. Aho" <user@example.net> - 2015-10-19 21:27 +0200
    Re: rawurlencode problem Derek Turner <frderek@suremail.je> - 2015-10-19 19:43 +0000
      Re: rawurlencode problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-20 00:03 +0200
      Re: rawurlencode problem "J.O. Aho" <user@example.net> - 2015-10-20 07:10 +0200
        Re: rawurlencode problem "J.O. Aho" <user@example.net> - 2015-10-20 07:21 +0200
          Re: rawurlencode problem Derek Turner <frderek@suremail.je> - 2015-10-20 08:29 +0000
            Re: rawurlencode problem "J.O. Aho" <user@example.net> - 2015-10-20 18:29 +0200
        Re: rawurlencode problem Arno Welzel <usenet@arnowelzel.de> - 2015-10-27 14:01 +0100
          Re: rawurlencode problem Arno Welzel <usenet@arnowelzel.de> - 2015-10-27 14:04 +0100
  Re: rawurlencode problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-20 00:00 +0200
  Re: rawurlencode problem Jerry Stuckle <jstucklex@attglobal.net> - 2015-10-19 19:35 -0400
    Re: rawurlencode problem Derek Turner <frderek@suremail.je> - 2015-10-20 08:34 +0000
      Re: rawurlencode problem Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-10-21 13:54 +0200

csiph-web