In addition to Chris's suggestions you should also alter the homeid
column (set default to NULL and update the whole database which
shouldn't be a problem) so you don't have to do a double check on the
same column. I would also suggest that the TSCN_MEDIAid column should be
an int not a varchar
Rob Adams wrote:
select h.addr, h.city, h.county, h.state, h.zip, 'yes' as show_prop,
h.askingprice, '' as year_built, h.rooms, h.baths,
'' as apt, '' as lot, h.sqft, h.listdate, '' as date_sold,
h.comments, h.mlsnum,
r.agency, concat(r.fname, ' ', r.lname) as rname,
r.phone as rph
Stut wrote:
Stut wrote:
Chris wrote:
Stut wrote:
Chris wrote:
Rob Adams wrote:
I have a query that I run using mysql that returns about 60,000
plus rows. It's been so large that I've just been testing it with
a limit 0, 1 (ten thousand) on the query. That used to take
about 10 minutes
Hi,
I would like to know if there is any setting that allows to connect to mysql
from php using SSL by default. I know that there is a flag MYSQL_CLIENT_SSL
in mysql_connect, however, I am trying to force PHP apps which I did *not*
wrote to transparently connect to mysql using SSL without having
At 01:18 23/07/2007, you wrote:
Message-ID: <[EMAIL PROTECTED]>
From: aldnin <[EMAIL PROTECTED]>
Subject: Re: [PHP-DB] PHP + PostgreSQL: invalid byte sequence for encoding
> This indicates that PHP not using UTF-8. That output is typical of
> UTF-8 output as Latin characters.
> I had similar p
select h.addr, h.city, h.county, h.state, h.zip, 'yes' as show_prop,
h.askingprice, '' as year_built, h.rooms, h.baths,
'' as apt, '' as lot, h.sqft, h.listdate, '' as date_sold, h.comments,
h.mlsnum,
r.agency, concat(r.fname, ' ', r.lname) as rname,
r.phone as rphone, '' as remail,
Stut wrote:
Chris wrote:
Stut wrote:
Chris wrote:
Rob Adams wrote:
I have a query that I run using mysql that returns about 60,000
plus rows. It's been so large that I've just been testing it with a
limit 0, 1 (ten thousand) on the query. That used to take
about 10 minutes to run, incl
Chris wrote:
Stut wrote:
Chris wrote:
Rob Adams wrote:
I have a query that I run using mysql that returns about 60,000 plus
rows. It's been so large that I've just been testing it with a limit
0, 1 (ten thousand) on the query. That used to take about 10
minutes to run, including process
