On Nov 27, 2010, at 1:24 PM, Don Wieland wrote:
On Nov 27, 2010, at 10:44 AM, Daniel P. Brown wrote:
Note how you keep changing case here. For example, m.aucciim_id
vs. m.AUCCIIM_ID. Also note that all of this is cAsE-sEnSiTiVe.
You are right. But it still chokes in PHP:
select m.* fr
On Nov 27, 2010, at 12:09 PM, Daniel P. Brown wrote:
At this point, can you just send the whole related snippet? The
cases keep changing and there's a lot of other suggestions that you
said you've tried. Just doing that on my local machine works without
error, so it's likely the result of anot
On Sat, Nov 27, 2010 at 14:45, Don Wieland wrote:
> Pretty please - I just want to get this working and move on ;-)
At this point, can you just send the whole related snippet? The
cases keep changing and there's a lot of other suggestions that you
said you've tried. Just doing that on my lo
On Nov 27, 2010, at 11:35 AM, Daniel P. Brown wrote:
Strange... I have no idea what to do. I got to run it via PHP.
Don, on which table is the column `member_year` located? Is that
on `Members`?
it is "Member_Years". I thought of that. I change the query:
select m.* from Members m inn
On Sat, Nov 27, 2010 at 14:30, Don Wieland wrote:
>
> Strange... I have no idea what to do. I got to run it via PHP.
Don, on which table is the column `member_year` located? Is that
on `Members`?
--
Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://
On Nov 27, 2010, at 10:39 AM, Tommy Pham wrote:
Don,
Have you tried to run the query in either MySQL workbench or the
command
line to ensure that query is SQL syntax error free? From the error
message,
it sounds more like a SQL syntax error. If you're able to run the
query
fine in the w
On Nov 27, 2010, at 10:44 AM, Daniel P. Brown wrote:
Note how you keep changing case here. For example, m.aucciim_id
vs. m.AUCCIIM_ID. Also note that all of this is cAsE-sEnSiTiVe.
You are right. But it still chokes in PHP:
select m.* from Members m inner join Member_Years my on m.AUCCII
On Sat, Nov 27, 2010 at 13:18, Don Wieland wrote:
> On Nov 27, 2010, at 10:07 AM, Bastien wrote:
>
>> Try removing the backticks around the table names. If you do use them,
>> then all values (field names and table names) need it.
>
> I tried that and still chokes...
>
> select m.* from Members m
> -Original Message-
> From: Don Wieland [mailto:d...@dwdataconcepts.com]
> Sent: Saturday, November 27, 2010 10:18 AM
> To: Bastien
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] Strange Query Error...
>
> On Nov 27, 2010, at 10:07 AM, Bastien wrote:
On Nov 27, 2010, at 10:08 AM, Daniel P. Brown wrote:
one primary question: are you using the mysql_*
family, mysqli_* family, or another method of interfacing with MySQL?
mysql_
$results = mysql_query($query) or die(mysql_error());
Don
--
PHP General Mailing List (http://www.php.net/)
To un
On Nov 27, 2010, at 10:07 AM, Bastien wrote:
Try removing the backticks around the table names. If you do use
them, then all values (field names and table names) need it.
I tried that and still chokes...
select m.* from Members m inner join Member_Years my on m.aucciim_id =
my.member_id wh
On Sat, Nov 27, 2010 at 12:30, Don Wieland wrote:
> Hi gang,
>
> I am executing a query via PHP that gives me a PHP error:
>
> You have an error in your SQL syntax; check the manual that corresponds to
> your MySQL server version for the right syntax to use near 'AND
> m.`Preferred_First_Name` LIK
On 2010-11-27, at 12:30 PM, Don Wieland wrote:
> Hi gang,
>
> I am executing a query via PHP that gives me a PHP error:
>
> You have an error in your SQL syntax; check the manual that corresponds to
> your MySQL server version for the right syntax to use near 'AND
> m.`Preferred_First_Name`
On Thu, 4 Nov 2004 13:02:19 -0700, Vail, Warren <[EMAIL PROTECTED]> wrote:
> It is too bad this clause is not supported by some of the other
> databases I have had to use
I think calling a limit a limit and an offset an offset is a good thing.
--
Greg Donald
Zend Certified Engineer
http://gdcon
Hey,
> the second
> specifies the maximum number of rows to return.
Thats where my problem was...thanks. I forget the Limit parameters, i for
some reason though the second parameter was till which record to return...
Loud and clear sign telling me to get some sleep (i guess)
:-)
Thanks,
Ryan
The second limit parameter is the actual number of rows to limit to, and in
most situations this is usually the same number (i.e. 0,15; 15,15; 30,15;
etc). It is too bad this clause is not supported by some of the other
databases I have had to use, it makes a convenient way of paging where the
sec
[snip]
$query = "select gallery_url,description from members limit
".$limit[0].",".$limit[1];
the first time: limit 0,15
and the second time: limit 16,30
[/snip]
from http://www.mysql.com/select
"The LIMIT clause can be used to constrain the number of rows returned
by the SELECT statement. LIM
17 matches
Mail list logo
