and throw your favorite Linux distro on it
(I'm not touching that holy war with a 10' eth0 cord)
I'll touch it.
It shouldn't be Fedora - Fedora has too short of a lifetime before major
version update is necessary to get patches. The main advantages of
Fedora are how new and shiny the deskt
> -Original Message-
> From: Wolf [mailto:lonew...@nc.rr.com]
> Sent: Monday, July 06, 2009 8:10 AM
>
> If you are running MySQL, go get a 486, put Fedora on it and
> use it for the heavy queries.
You didn't seriously just tell someone to use an ancient-ass __80486__ PC
for their "hea
On Mon, Jul 6, 2009 at 11:15, Miller,
Terion wrote:
>
> It seems like Pagination except I already have that in place for all records,
> so maybe I'm just looking for a way to page the search results...
> Boss kept referring to "partitioning results"
By definition, yes, but if you use the term
On 7/6/09 10:07 AM, "Daniel Brown" wrote:
On Mon, Jul 6, 2009 at 10:48, Miller,
Terion wrote:
> Ok, say you have a database with 16000 records in it, but you only want to
> call out say 2000 records at a time as the search/query is performed, then
> store the first 2000 in a session and then r
"Miller wrote:
> Ok, say you have a database with 16000 records in it, but you only want to
> call out say 2000 records at a time as the search/query is performed, then
> store the first 2000 in a session and then retrieve the next 2000 etc etc as
> a way to minimize server strain?
>
> (I'm
On Mon, Jul 6, 2009 at 10:48, Miller,
Terion wrote:
> Ok, say you have a database with 16000 records in it, but you only want to
> call out say 2000 records at a time as the search/query is performed, then
> store the first 2000 in a session and then retrieve the next 2000 etc etc as
> a way to min
2009/7/6 Miller, Terion :
> Ok, say you have a database with 16000 records in it, but you only want to
> call out say 2000 records at a time as the search/query is performed, then
> store the first 2000 in a session and then retrieve the next 2000 etc etc as
> a way to minimize server strain?
>
> (
Ok, say you have a database with 16000 records in it, but you only want to
call out say 2000 records at a time as the search/query is performed, then
store the first 2000 in a session and then retrieve the next 2000 etc etc as
a way to minimize server strain?
(I'm tasked to do this and )
1. do
8 matches
Mail list logo
