RE: odd problem with select as statement

2010-12-20 Thread Ramsey, Robert L
amsey, Robert L Cc: mysql@lists.mysql.com Subject: Re: odd problem with select as statement i.e. just try this: mysql> select 4E5664736F400E8B482EA7AA67853D13; ERROR 1367 (22007): Illegal double '4E5664736' value found during parsing -Hank On Mon, Dec 20, 2010 at 12:50 PM, Hank mailto:

Re: odd problem with select as statement

2010-12-20 Thread Hank
i.e. just try this: mysql> select 4E5664736F400E8B482EA7AA67853D13; ERROR 1367 (22007): Illegal double '4E5664736' value found during parsing -Hank On Mon, Dec 20, 2010 at 12:50 PM, Hank wrote: > > Here's my 5 second guess.. > > 4E5664736... is being interpreted as a number in scientific no

Re: odd problem with select as statement

2010-12-20 Thread Hank
Here's my 5 second guess.. 4E5664736... is being interpreted as a number in scientific notation .. i.e. 4*10^5664736 and the parser doesn't like that as a field name. -Hank On Mon, Dec 20, 2010 at 12:43 PM, Ramsey, Robert L wrote: > I am having the hardest time getting a select as statement

Re: odd problem with select as statement

2010-12-20 Thread Johnny Withers
I can't tell you 'why' it is occurring when the field name begins with 4E5, but you can solve your problem by enclosing all your field names in backticks ( ` ). IE: SELECT field AS `4E5664736F400E8B482EA7AA67853D13` On Mon, Dec 20, 2010 at 11:43 AM, Ramsey, Robert L wrote: > I am having the h

odd problem with select as statement

2010-12-20 Thread Ramsey, Robert L
I am having the hardest time getting a select as statement right. Here is the full query: select SUM(IF(image='EE0840D00E2ED8A317E5FA9899C48C19',1,0)) as EE0840D00E2ED8A317E5FA9899C48C19, SUM(IF(image='235C7987796D5B7CEBF56FBDA2BF7815',1,0)) as 235C7987796D5B7CEBF56FBDA2BF7815, SUM(IF(image='9

RE: ~problem with select into outfile~

2006-04-13 Thread Addison, Mark
From: Mohammed Abdul Azeem Sent: 13 April 2006 07:29 > > Hi > > Iam having a problem using "select into outfile" command, iam getting > the following error. can anyone help me trace the problem. > > mysql> SELECT * INTO OUTFILE'/home/public1/data.txt' FROM temp_table > WHERE last_time_update =

~problem with select into outfile~

2006-04-12 Thread Mohammed Abdul Azeem
Hi Iam having a problem using "select into outfile" command, iam getting the following error. can anyone help me trace the problem. mysql> SELECT * INTO OUTFILE'/home/public1/data.txt' FROM temp_table WHERE last_time_update = "2006-04-01"; ERROR 1 (HY000): Can't create/write to file '/home/publi

Re: [PHP] RE: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-02 Thread Richard Lynch
Matt Babineau wrote: > Ok I installed PHP 4.3.10 and it still has not fixed the problem. If I > remove the SQL_CALC_FOUND_ROWS from the query, it works no problems! This > is > very strange behavior! Not really that strange, I think... While you might want to read this: http://us4.php.net/manual

Re: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-02 Thread Jigal van Hemert
A quick look at the PHP site... http://www.php.net/manual/en/faq.databases.php#faq.databases.upgraded Regards, Jigal. - Original Message - From: "Matt Babineau" <[EMAIL PROTECTED]> To: "'MySQL General'" Sent: Tuesday, February 01, 2005

RE: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Matt Babineau
: Michael Stassen [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 3:55 PM To: Michael Dykman Cc: Matt Babineau; 'MySQL General' Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS I'm confused. That bug was closed over 2 years ago. What makes you think it applies here, and

Re: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Michael Stassen
e what happens? Matt Babineau Criticalcode w: http://www.criticalcode.com p: 858.733.0160 e: [EMAIL PROTECTED] -Original Message- From: Michael Dykman [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 12:47 PM To: Matt Babineau Cc: 'MySQL General' Subject: Re: Problem with SE

RE: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Michael Dykman
al Message- > From: Michael Dykman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 01, 2005 12:47 PM > To: Matt Babineau > Cc: 'MySQL General' > Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS > > Matt, > > I suspect your problem is PHP, not My

RE: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Matt Babineau
- From: Matt Babineau [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 12:52 PM To: 'Michael Dykman' Cc: 'MySQL General' Subject: RE: Problem with SELECT SQL_CALC_FOUND_ROWS Weird thing is that I am running PHP 4.3.9I guess I can upgrade and see what happ

RE: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Matt Babineau
:47 PM To: Matt Babineau Cc: 'MySQL General' Subject: Re: Problem with SELECT SQL_CALC_FOUND_ROWS Matt, I suspect your problem is PHP, not MySQL. refer to http://bugs.php.net/bug.php?id=16906&edit=1 On Tue, 2005-02-01 at 15:20, Matt Babineau wrote: > Hi All- > &

Re: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Michael Dykman
Matt, I suspect your problem is PHP, not MySQL. refer to http://bugs.php.net/bug.php?id=16906&edit=1 On Tue, 2005-02-01 at 15:20, Matt Babineau wrote: > Hi All- > > I'm running a query that uses SQL_CALC_FOUND_ROWS for my search engine on a > real estate site. The problem is that I get

RE: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Matt Babineau
ry(); statement. Matt Babineau Criticalcode w: http://www.criticalcode.com <http://www.criticalcode.com/> p: 858.733.0160 e: [EMAIL PROTECTED] _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 01, 2005 12:25 PM To: Matt Babineau Cc: 'MySQL

Re: Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread SGreen
"Matt Babineau" <[EMAIL PROTECTED]> wrote on 02/01/2005 03:20:49 PM: > Hi All- > > I'm running a query that uses SQL_CALC_FOUND_ROWS for my search engine on a > real estate site. The problem is that I get an error when I run my query: > > "Warning mysql_query(): Unable to save result set in /

Problem with SELECT SQL_CALC_FOUND_ROWS

2005-02-01 Thread Matt Babineau
Hi All- I'm running a query that uses SQL_CALC_FOUND_ROWS for my search engine on a real estate site. The problem is that I get an error when I run my query: "Warning mysql_query(): Unable to save result set in /clients/search.php" My Query is: SELECT SQL_CALC_FOUND_ROWS propertyData.*, propert

Re: 4.1.1 Problem with SELECT INTO OUTFILE

2004-03-05 Thread Egor Egorov
Chris Fossenier <[EMAIL PROTECTED]> wrote: > > It seems that each time we select into an OUTFILE that already exists > (re-use a name) the server crashes. > > Anyone have any ideas if this is a setting or just a bug? It's known bug: http://bugs.mysql.com/bug.php?id=2123 -- For techni

4.1.1 Problem with SELECT INTO OUTFILE

2004-03-05 Thread Chris Fossenier
It seems that each time we select into an OUTFILE that already exists (re-use a name) the server crashes. Anyone have any ideas if this is a setting or just a bug? Thanks. Chris.

Re: MySQL 5 problem with select and stored procs

2004-01-17 Thread matthew.darby
has posted with the same issue in Mysql 5. Any help appreciated. - Original Message - From: "Aleksandar Bradaric" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, January 16, 2004 1:15 PM Subject: Re: MySQL 5 problem with sele

Re: MySQL 5 problem with select and stored procs

2004-01-16 Thread Aleksandar Bradaric
Hi, > Any ideas why it's looking for the table .1? Could you post your query? Take care, Aleksandar -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]

MySQL 5 problem with select and stored procs

2004-01-16 Thread matthew.darby
Hello I've installed MySQL 5 and I seem to have a couple of problems with it (or it does with me). After installing into a clean environment I created a new server (rm_development) in the Control Center, and then created a new database. The first problem/query is after having created a table

Re: Problem with SELECT

2003-06-18 Thread gerald_clark
Muazzam Siddiqui wrote: Hi, I am getting the error You have an error in your SQL syntax near 'select max(news_id) from news)' at line 1 while trying to run this query. SELECT * FROM News where News_ID = (SELECT MAX(News_ID) FROM News); You don't say what version of MySQL you are running. You

Problem with SELECT

2003-06-18 Thread Muazzam Siddiqui
Hi, I am getting the error You have an error in your SQL syntax near 'select max(news_id) from news)' at line 1 while trying to run this query. SELECT * FROM News where News_ID = (SELECT MAX(News_ID) FROM News); The table type is INNODB. Is it some MySQL related problem because I know the quer

RE: Null problem with SELECT

2003-06-03 Thread Mike Hillyer
bmysql.com -Original Message- From: Sparky Kopetzky [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 3:24 PM To: My Sql List Subject: Null problem with SELECT Greetings! I have a query for a report that accesses columns that could possibly be null. Here's an example: SELECT blah, blah,

Null problem with SELECT

2003-06-03 Thread Sparky Kopetzky
Greetings! I have a query for a report that accesses columns that could possibly be null. Here's an example: SELECT blah, blah, blah FROM bite bite, person agency WHERE bite.bite_id = "AC-2003-0004" AND agency.person_id = bite.bite_agency_id; bite.bite_agency_id and other fields like this could

Re:Re: Re:Re: A little problem with SELECT

2003-01-17 Thread nossareh
Marcos Henke Wrote: > SELECT a.* FROM company a, employee b > WHERE a.id=b.cid AND > (b.name='joe' OR > b.name='bill'); This will pull out all companies which have a Joe or a Bill. We want only the company in which Joe and Bill are working. A working solution was offered by Adolfo Bello earl

Re: A little problem with SELECT

2003-01-17 Thread Marcos Henke
"Blaster" <[EMAIL PROTECTED]> Sent: Friday, January 17, 2003 7:51 AM Subject: Re: A little problem with SELECT > * Blaster > [...] > > "main" company table > > id (int) | company name (varchar) | phone (varchar) | .. more fields that > > doesn't r

Re: A little problem with SELECT

2003-01-17 Thread Roger Baklund
* Blaster [...] > "main" company table > id (int) | company name (varchar) | phone (varchar) | .. more fields that > doesn't really matter > > "employee" table (company.id = employee.cid) > id (int) | cid (int) | name (varchar) | age (int) | email (varchar) > > Now, I want to make a search which ca

Re: A little problem with SELECT

2003-01-16 Thread Adolfo Bello
> SELECT a.* FROM company a, employee b WHERE a.id=b.cid AND b.name='joe' OR > b.name='bill'; > however, this would return any companies that has ONLY one Bill or one Joe > .. I only want companies that > have BOTH. It also returns one row with the company per name it found, so > you can imagin

A little problem with SELECT

2003-01-16 Thread Blaster
Hello, I have a really tough problem here, I can't think of a way to make this work Imagine 2 tables, the first one is the "main" table where I keep listings of companies and "general" info about them. In the second table, I keep 1 row for each employee and an field which points to the company

Re: LOCK problem with SELECT table alias

2003-01-05 Thread Christian Kohlschuetter
Am Sonntag, 5. Januar 2003 19:29 schrieb Paul DuBois: > At 14:45 +0100 1/5/03, [EMAIL PROTECTED] wrote: > > >Description: > > > > A SELECT statement fails if you have table aliases and use > > table locking with the LOCK command > > This is not a bug. It's documented in the manual that y

Re: Re: LOCK problem with SELECT table alias

2003-01-05 Thread Paul DuBois
At 14:45 +0100 1/5/03, [EMAIL PROTECTED] wrote: >Description: A SELECT statement fails if you have table aliases and use table locking with the LOCK command This is not a bug. It's documented in the manual that you must lock all the tables at once that you intend to use, *including* locking

LOCK problem with SELECT table alias

2003-01-05 Thread ck
mes. >Submitter-Id: >Originator:Christian Kohlschuetter >Organization: NewsClub.de >MySQL support: none >Synopsis: Locking problem with SELECT-aliases >Severity: serious >Priority: high >Category: mysql >Class: sw-bug >Release: mysql-4.

RE: Problem with select.

2002-10-26 Thread Gordon
Wednesday, October 23, 2002 9:47 AM > To: [EMAIL PROTECTED] > Subject: Problem with select. > > > HI, > I don't know is it bad or not but I face queries the work > quite long time. > > the sql is : > select * from log_answers_index limit 0,10 > > and it tak

Re: Problem with select.

2002-10-24 Thread Sinisa Milivojevic
On Wed, 23 Oct 2002 19:15:59 +0300 "Andrey Hristov" <[EMAIL PROTECTED]> wrote: > I am not an expert but I think that when there is not order by the > output is sorted on the primary key. > So : select * from log_answers_index limit 0,10 and select * from > log_ansers_index where log_entry_id be

Re: Problem with select.

2002-10-23 Thread gerald_clark
wrote: - Original Message - From: "gerald_clark" <[EMAIL PROTECTED]> To: "Andrey Hristov" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 23, 2002 6:23 PM Subject: Re: Problem with select. Andrey Hristov wrote: HI, I

Re: Problem with select.

2002-10-23 Thread Andrey Hristov
- Original Message - From: "gerald_clark" <[EMAIL PROTECTED]> To: "Andrey Hristov" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, October 23, 2002 6:23 PM Subject: Re: Problem with select. > > > Andrey Hristov wrote: >

Re: Problem with select.

2002-10-23 Thread gerald_clark
Andrey Hristov wrote: HI, I don't know is it bad or not but I face queries the work quite long time. the sql is : select * from log_answers_index limit 0,10 and it takes too much time for me to receive the result. I got indexes on most of the fields, i got primary key which is auto_increment

Problem with select.

2002-10-23 Thread Andrey Hristov
HI, I don't know is it bad or not but I face queries the work quite long time. the sql is : select * from log_answers_index limit 0,10 and it takes too much time for me to receive the result. I got indexes on most of the fields, i got primary key which is auto_increment int(11). When I did expla

Re: Problem with SELECT

2002-05-02 Thread Dicky Wahyu Purnomo
On Thu, 02 May 2002 13:11:23 +0400 "Sheni R. Meledath" <[EMAIL PROTECTED]> wrote: > Using the second command I can't display all the records. > > But using separate select statement I can select & display any record which > is not displayed in the above case. > ### > $result=mysql_query("selec

Re: Problem with SELECT

2002-05-02 Thread Sheni R. Meledath
Many Thanks for your quick reply. The MySQL version is 3.22 on Unix/FreeBSD/Apache. thanks At 08:43 AM 5/2/02 -0500, Gerald Clark wrote: >Unfortunately, you did not tell us what version you are running, or what >platform you are running it on. > > >Try rebuilding the indexes with myisamchk or

Re: Problem with SELECT

2002-05-02 Thread Gerald Clark
Unfortunately, you did not tell us what version you are running, or what platform you are running it on. Try rebuilding the indexes with myisamchk or whatever is appropriate for your table type. Sheni R. Meledath wrote: > Hello: > > I have a problem while selecting the records from a table.

Problem with SELECT

2002-05-02 Thread Sheni R. Meledath
Hello: I have a problem while selecting the records from a table. This table has got 15494 records. But when selecting its displaying only 1745 records. ### $result=mysql_query("SELECT COUNT(*) as numrows FROM $table2"); $row=mysql_fetch_array($result); $num_rows2 = $row[numrows]; echo $num_row

Problem with select statements in Visual Basic

2002-04-22 Thread Langrehr, Trevor
I have a problem in VB trying to use select statements with MySQL. My problem does not occur only with the example below but with ANY select statement I try to make against my MySQL database. Much thanks in advance to anyone that can help me out with this :) This is my code: Private Sub optNoTec

Re: problem with select ... in share mode

2001-05-02 Thread Heikki Tuuri
Hi! It is a bug in the parser that it does not accept ... IN SHARE MODE immediately after a WHERE clause. I think yacc is not very sophisticated in lookahead of symbols when it is trying to parse a statement, and may confuse IN SHARE MODE to WHERE colA IN (). We will fix the parser, but mean

problem with select ... in share mode

2001-05-02 Thread Michael Kofler
3.23.37: SELECT * FROM table1 WHERE colA=1 IN SHARE MODE does not work (ERROR 1064: You have an error in your SQL syntax near 'share mode' at line 1). On the other side SELECT * FROM table1 IN SHARE MODE does work, i.e. the syntax error only happens if I specify a WHERE clause or an OR

Re: newbie: problem with "select in (select)"

2001-02-05 Thread René Tegel
go to www.codecity.com mysql just does not support in :((( it's good, but far for 'sql compliant'... gl rene - Original Message - From: "Henrik Lebtien Mohr" <[EMAIL PROTECTED]> To: "MySQL List" <[EMAIL PROTECTED]> Sent: Monday, February

newbie: problem with "select in (select)"

2001-02-05 Thread Henrik Lebtien Mohr
Hi again If I try the following on my MySQL DB, I get an error: select user_id from tblUser where user_id in (select user_id from tblUserLink where group_id = xx) xx is an integer defining which group_id we want info on (mediumint(9)) user_id in tblUser and tblUserLink is also defined as medium