Re: Re: Problem with query

Jim Giner <[email protected]>
Newsgroups gmane.comp.php.database
Message-ID <[email protected]>
On 6/25/2013 6:06 AM, Toby Hart Dyke wrote:
>
> What Jim means is here in the manual:
>
> http://www.php.net/manual/en/language.types.array.php#language.types.array.donts
>
>
> In a nutshell:
>
> Always use quotes around a string literal array index. For example,
> /$foo['bar']/ is correct, while /$foo[bar]/ is not.
>
> The reason is that without the quotes, you are generating an undefined
> constant (bar) rather than using a string index ('bar'). It works, but
> could have side effects in the future, so it's bad form to do it.
>
> As for general politeness, you seem to be unaware of recent history in
> this (an associated) groups. The OP has often committed the ultimate
> sine. Not posting slightly wild code (we've all been/are there!) He
> doesn't seem to listen or learn too well. Many posters (including Jim)
> have offered a lot of of extremely good (and detailed) advice which
> seems to be rarely taken...
>
>    Toby
>
>
> On 6/25/2013 7:32 AM, OJFR wrote:
>> Yeah, Jim, please explain what u mean by "Per the manual, associative
>> arrays
>> using string indices should always use ' ' around them.  They work (as
>> mentioned in the manual) but are wrong". As long as I remember  I
>> could use
>> associative arrays in that way (ex. $_SESSION['Cust_Num']). There's
>> another
>> way to do that using string indices? Why do you say it's wrong? It's
>> obsolete?
>>
>> I would like to make a call to all the members of this mailing list:
>> knowledge is a wonderful gift so, why we don't share it politely and
>> efficiency. Jim, I will take you as an example. You start saying "
>> Against
>> my better judgement, here I go again".
>
>
My humble thanks for your timely support.  :)

-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.