Tommy Pham wrote:
It turns out the issue was actually in the pagination... I'm reworking the
> whole thing and stream lining it... But in the pagination that I found on
> the internet it used a "SELECT COUNT(*) WHERE state='{$state}'"; and the
> COUNT was killing the time... Once that was remo
On Wed, Oct 26, 2011 at 12:52 AM, Lester Caine wrote:
> Tommy Pham wrote:
>
>> It turns out the issue was actually in the pagination... I'm reworking the
>>> > whole thing and stream lining it... But in the pagination that I found
>>> on
>>> > the internet it used a "SELECT COUNT(*) WHERE state
Tommy Pham wrote:
I wonder ... The real question is what's the purpose of the DB? Is it for OLAP
or OLTP? ;)
As for dealing with DB having millions of rows, you're crossing over into DBA
area.
Many of my customers have coming up on 20 years of data available. There has
been a debate on trans
On Wed, Oct 26, 2011 at 1:40 AM, Lester Caine wrote:
> Tommy Pham wrote:
>
>> I wonder ... The real question is what's the purpose of the DB? Is it for
>> OLAP
>> or OLTP? ;)
>> As for dealing with DB having millions of rows, you're crossing over into
>> DBA area.
>>
>
> Many of my customers hav
On Wed, Oct 26, 2011 at 3:23 AM, Tommy Pham wrote:
> On Wed, Oct 26, 2011 at 1:40 AM, Lester Caine wrote:
>
>> Tommy Pham wrote:
>>
>>> I wonder ... The real question is what's the purpose of the DB? Is it
>>> for OLAP
>>> or OLTP? ;)
>>> As for dealing with DB having millions of rows, you're c
Tommy Pham wrote:
Many of my customers have coming up on 20 years of data available. There has
been a debate on transferring historic data to a separate database, but
having it available is not causing a problem, except for some counts and
larger search actions, and being able to
Hello all.
I inherited some PHP pages about a year ago. They have been fine all
along but now a bunch of erroneous errors and results are popping up.
I traced it to the way the variables were being used on the page...
for example, the following SQL statement (a space between ' and " for
Rick Dwyer wrote:
Hello all.
I inherited some PHP pages about a year ago. They have been fine all along but
now a bunch of erroneous errors and results are popping up. I traced it to the
way the variables were being used on the page... for example, the following SQL
statement (a space between '
On 10/26/2011 07:20 AM, Rick Dwyer wrote:
> Hello all.
>
> I inherited some PHP pages about a year ago. They have been fine all
> along but now a bunch of erroneous errors and results are popping up. I
> traced it to the way the variables were being used on the page... for
> example, the followi
On Wed, Oct 26, 2011 at 4:14 AM, Lester Caine wrote:
> Tommy Pham wrote:
>
>>
>>Many of my customers have coming up on 20 years of data available.
>> There has
>>been a debate on transferring historic data to a separate database, but
>>having it available is not causing a problem, exc
Jason Pruim
li...@pruimphotography.com
On Oct 26, 2011, at 6:23 AM, Tommy Pham wrote:
> On Wed, Oct 26, 2011 at 1:40 AM, Lester Caine wrote:
>
>> Tommy Pham wrote:
>>
>>> I wonder ... The real question is what's the purpose of the DB? Is it for
>>> OLAP
>>> or OLTP? ;)
>>> As for dealing w
Your boss wants to give access to phone numbers to the public in general?
Then what?
Glad mine's unlisted.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Jason Pruim
li...@pruimphotography.com
On Oct 26, 2011, at 9:09 PM, Jim Giner wrote:
> Your boss wants to give access to phone numbers to the public in general?
> Then what?
>
> Glad mine's unlisted.
There's no identifying information on the phone numbers... Simply just the
phone number...
13 matches
Mail list logo
