- Original Message -
From: Javier Yévenez jyeve...@gmail.com
If the field db1.table1.field1 has the same name that the field
db2.table1.field1, maybe you have to use an alias for each table:
No, he's using a subquery, those fields cannot be referenced.
--
Bier met grenadyn
Is als
- Original Message -
From: Shawn Green (MySQL) shawn.l.gr...@oracle.com
Simple math (set theory) suggests that all of the values of field1 on
db2.table1 contain only copies or duplicates of the field1 values in
the rows in db1.table1.
Shawn,
The select count(distinct)s show that
Hi Mike,
On 11/8/2011 20:46, Mike Seda wrote:
All,
Can anyone out there explain the result of the third statement provided
below:
mysql select count(distinct field1) from db1.table1;
++
| count(distinct field1) |
++
| 1063 |
Hi,
mysql select count(distinct field1) from db2.table1 where field1 not in
(select field1 from db1.table1);
++
| count(distinct field1) |
++
If the field db1.table1.field1 has the same name that the field
db2.table1.field1, maybe you have
09, 2011 7:19 AM
*To:* Shawn Green (MySQL)
*Cc:* Mike Seda; mysql@lists.mysql.com; Rong Chen
*Subject:* Re: Issue With Subqueries
Hi,
mysql select count(distinct field1) from db2.table1 where
field1 not in
(select field1 from db1.table1
All,
Can anyone out there explain the result of the third statement provided
below:
mysql select count(distinct field1) from db1.table1;
++
| count(distinct field1) |
++
| 1063 |
++
1 row in set (0.01
Hello All,
Tables:
# relevant fields
invitations: donation_pledge, paid (boolean), currency_id
currencies: code
I am trying to subtract the paid amounts from the amounts pledged using a
subquery in the FROM clause but am having problems and am going blind. Plus,
My SQL is weak at present.
I
condition on the currency between
the subquery and the other tables. This would explain why the 70 is
subtracted not only from the BRL value but also from the EUR.
Off-hand, I have no explanation for the doubling of the sums, but I have
never used subqueries in the FROM clause.
Others might know
-hand, I have no explanation for the doubling of the sums, but I have
never used subqueries in the FROM clause.
Others might know more about this, but telling the version you are using
might be helpful for them.
That said, IMO you are doing it much more complicated than necessary:
As your
Hi all,
I'm hoping someone can help me with this please.
Is there a way to total counts done in subqueries?
So I want to do:
-=-=-=-=-=-=-=
SELECT
`Notes`.`note_id`,
`Notes`.`last_updated_datetime`,
`Notes`.`event_date`,
`Notes`.`subject`,
`Notes`.`summary`,
`Notes`.`content`,
(SELECT
Is there a way to total counts done in subqueries?
Select expression aliases can't be referenced at the same level. You
have to create another outer level ...
SELECT
note_id, last_updated_datetime,event_date,subject,summary,content,
linked_issues_count,linked_people_count
Peter Brawley wrote:
Is there a way to total counts done in subqueries?
Select expression aliases can't be referenced at the same level. You
have to create another outer level ...
alternatively use variables:
mysql select @first := 1 as value1, @second := 2 as value2,
@fir...@second
Thanks Nigel and Peter, I went for Nigel's solution below. Both very
useful, learnt a lot, thank you.
Cheers,
Nigel
nigel wood wrote:
Is there a way to total counts done in subqueries?
Never done this but my educated guess is:
SELECT
`Notes`.`note_id`,
`Notes`.`last_updated_datetime
mrc_titles is a temp table?
On Wed, Oct 15, 2008 at 11:59 PM, Jerry Schwartz [EMAIL PROTECTED]
wrote:
I tried to make a query that joins to subqueries:
SELECT discontinued.b
FROM
(SELECT mrc_titles.title AS a
FROM mrc_titles JOIN prod ON mrc_titles.title
I tried to make a query that joins to subqueries:
SELECT discontinued.b
FROM
(SELECT mrc_titles.title AS a
FROM mrc_titles JOIN prod ON mrc_titles.title = prod.prod_title
JOIN pub ON prod.pub_id = pub.pub_id
WHERE pub.pub_code = MRC
guys,
strange things happen when using COUNT() in subqueries. even the use of
HAVING in a SELECT statement turns up a weired result, as it should work
on the result set and should be filtered while rows are returned to the
client.
(you can find the selects and stuff in a more readable way
I'm not (yet) using sub-queries since the old version of MySQL were
unable to handle them, then I was using 'join'.
I wish to know if it's possibile to do all what I did with 'join'
with subqueries.
and which one is faster/better to use?
for example it'd be possibile to 'translate
, then I was using 'join'.
I wish to know if it's possibile to do all what I did with 'join'
with subqueries.
and which one is faster/better to use?
for example it'd be possibile to 'translate' that using subselect?
SELECT Esercente.Insegna, Terminale.TermId, Abilitazione.CodCarta
table);
Ref: http://dev.mysql.com/doc/refman/5.0/en/any-in-some-
subqueries.html
Thanks
ViSolve DB Team
- Original Message -
From: Ben Lachman [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Sunday, September 03, 2006 10:33 AM
Subject: IN ANY subqueries
I
- Original Message -
From: Ben Lachman [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Sunday, September 03, 2006 10:33 AM
Subject: IN ANY subqueries
I have a string comparison that I would like to do against a short
list of constant strings.
at the moment I am using the syntax
SELECT
2006/9/4, [EMAIL PROTECTED] [EMAIL PROTECTED]:
Hello all,
I need to perform an SQL statement over 5 different tables, with complex
request. To do so, i'm using subqueries.
SELECT ... FROM (SELECT .WHERE) as T1 LEFT JOIN (SELECT
.WHERE) as T2 WHERE .
The problem
@lists.mysql.com
Sent: Sunday, September 03, 2006 10:33 AM
Subject: IN ANY subqueries
I have a string comparison that I would like to do against a short
list of constant strings.
at the moment I am using the syntax
SELECT id FROM t1 WHERE name IN('s1', 's2', 's3', ...);
However, this limits me
Hello all,
I need to perform an SQL statement over 5 different tables, with complex
request. To do so, i'm using subqueries.
SELECT ... FROM (SELECT .WHERE) as T1 LEFT JOIN (SELECT
.WHERE) as T2 WHERE .
The problem is that only JOIN seems working with subqueries (LEFT
://dev.mysql.com/doc/refman/5.0/en/any-in-some-
subqueries.html
Thanks
ViSolve DB Team
- Original Message -
From: Ben Lachman [EMAIL PROTECTED]
To: mysql@lists.mysql.com
Sent: Sunday, September 03, 2006 10:33 AM
Subject: IN ANY subqueries
I have a string comparison that I would like
I have a string comparison that I would like to do against a short
list of constant strings.
at the moment I am using the syntax
SELECT id FROM t1 WHERE name IN('s1', 's2', 's3', ...);
However, this limits me to exact matches and I'd like to move to a
caparison expersion that lets me match
Hi,
I have a query like this:
SELECT table1.*,(
SELECT COUNT( field2 )
FROM table2
WHERE id=10
) AS total
FROM table1
GROUP BY id
LIMIT 1
but the subqueries do not work with mysql 4.1. How can I convert it
(or make to work) in MySQL 3.x, 4.0 possibly in one only query?
thanks
--
http
See http://dev.mysql.com/doc/refman/5.0/en/rewriting-subqueries.html
for some tips
Dan
On 8/23/06, spacemarc [EMAIL PROTECTED] wrote:
Hi,
I have a query like this:
SELECT table1.*,(
SELECT COUNT( field2 )
FROM table2
WHERE id=10
) AS total
FROM table1
GROUP BY id
LIMIT 1
but the subqueries
On Wed, 2006-08-23 at 22:23 +0200, spacemarc wrote:
Hi,
I have a query like this:
SELECT table1.*,(
SELECT COUNT( field2 )
FROM table2
WHERE id=10
) AS total
FROM table1
GROUP BY id
LIMIT 1
but the subqueries do not work with mysql 4.1. How can I convert it
(or make to work
--- Daevid Vincent [EMAIL PROTECTED] wrote:
Well I think this is mostly working. I have a 'NULL' user ID which is
'system' that I need to get into here, but I think I'm mostly on
track...
There are lots of ways to accomplish this task it seems. ALL of which
would
be so much easier if
vmware reviewit # mysql --version
mysql Ver 14.12 Distrib 5.0.19, for pc-linux-gnu (i686) using readline 5.1
Given two tables:
CREATE TABLE `logs` (
`id` bigint(20) unsigned NOT NULL auto_increment,
`user_id` int(10) unsigned default '0',
`created_on` timestamp
On 4/28/06, Daevid Vincent [EMAIL PROTECTED] wrote:
vmware reviewit # mysql --version
mysql Ver 14.12 Distrib 5.0.19, for pc-linux-gnu (i686) using readline
5.1
Given two tables:
CREATE TABLE `logs` (
`id` bigint(20) unsigned NOT NULL auto_increment,
`user_id`
-Original Message-
From: Alex Arul [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 27, 2006 11:28 PM
To: Daevid Vincent
Cc: mysql@lists.mysql.com
Subject: Re: Help with subqueries...
On 4/28/06, Daevid Vincent [EMAIL PROTECTED] wrote:
vmware reviewit # mysql --version
Thanks Alex, that got me started. I don't understand why I
had to use IN
when the example uses = but at least it kinda works...
The problem is now that I can't get the right data.
mysql select max(created_on), user_id, id from logs group by user_id;
|
+-+-+-++--+
From: Alex Arul [mailto:[EMAIL PROTECTED]
Sent: Friday, April 28, 2006 2:18 AM
To: Daevid Vincent
Subject: Re: Help with subqueries... MAX
On Fri, 2006-04-28 at 00:13 -0700, Daevid Vincent wrote:
The problem is now that I can't get the right data.
mysql select max(created_on), user_id, id from logs group by user_id;
+-+-++
| max(created_on) | user_id | id |
I was fooling around, learning subqueries, group by and everything
unearthing my mental unknowns of SQL world. So I thought I would
divide total letters of the entire bible by total numbers of books,
chapters and verses. Here is what I came up with the best
optimization possible to my knowledge
Hello!
another simpler solution :
...
Thanks, Mathias!
You helped me greatly!
Now my program works as desired.
--
Good luck!
Vladimir
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
--
MySQL General Mailing List
For list
Hello!
MySQL v. 4.1.11.
I'm trying to write a subquery, MySQL says Error.
select num, theme, intro
from vt_(select pnid from vt_partition where pnid regexp '^[0-9]{11}$')
order by date desc, timer desc;
describe vt_parition:
+--+--+--+-+--++
admin [EMAIL PROTECTED] wrote on 06/14/2005 01:01:33 PM:
Hello!
MySQL v. 4.1.11.
I'm trying to write a subquery, MySQL says Error.
select num, theme, intro
from vt_(select pnid from vt_partition where pnid regexp '^[0-9]{11}$')
order by date desc, timer desc;
describe vt_parition:
.
Rhino
-Original Message-
From: admin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 14, 2005 1:02 PM
To: mysql@lists.mysql.com
Cc: mysql@lists.mysql.com
Subject: How to write subqueries?
Hello!
MySQL v. 4.1.11.
I'm trying to write a subquery, MySQL says Error.
select num, theme, intro
@lists.mysql.com
Subject: Re: How to write subqueries?
admin [EMAIL PROTECTED] wrote on 06/14/2005 01:01:33 PM:
Hello!
MySQL v. 4.1.11.
I'm trying to write a subquery, MySQL says Error.
select num, theme, intro
from vt_(select pnid from vt_partition where pnid regexp '^[0-9]{11}$')
order
Hello,
You forgot a parenthesis in the regexp function.
Second, if you construct your query with prepared statements, you can do it :
mysql insert into vt_partition(pnid) values('01234567890');
mysql select concat('vt_',pnid) into @tbl from vt_parition where pnid regexp
('^[0-9]{11}$') ;
mysql
Hello!
Many thanks to everybody who tried to help me!
N.B. you should have only one pnid to make your query work (UNIQUE pnid),
or LIMIT the result of the subquery by LIMIT 1.
I need to do the following:
Get one or more than one pnid from vt_partition and then make queries to the
vt_pnid
You're welcome.
if you have more than one pnid, you should use perl or php. then use a loop to
manage each pnid query, then send it to the server, and use it's result.
another simpler solution :
mysql create table sql as select concat('vt_',pnid) tbl from vt_parition where
pnid regexp
Jochem van Dieten wrote:
Also, let's not mistake the means for the goal. Using indexes is just
a way to solve it and there may be other fixes. The goal is to improve
performance.
no.. using indexes is THE way to fix it :)
I don't want a subquery scanning all 700 million rows in my table
On 6/9/05, Kevin Burton wrote:
Jeff Smelser wrote:
Thats funny.. looks like it will be added to 5.1.. Dunno why they
think fixing
it is adding a feature..
WOW! That's just insane! This seriously has to be fixed in 5.0 or sooner...
Chill out man. It is not like it is returning the wrong
[snip]
I think MySQL has a little ways to go yet before I would subjectively
call
it best.
I posted twice to the list with questions about porting my application
that
runs on (SQL Server, Oracle, PostgreSQL, Sybase SQL Anywhere, MS Access,
and
DB2) to MySQL. No one on the mysql list, or the
I think MySQL has a little ways to go yet before I would subjectively
call it best.
I posted twice to the list with questions about porting my application
that
runs on (SQL Server, Oracle, PostgreSQL, Sybase SQL Anywhere, MS Access,
and
DB2) to MySQL. No one on the mysql list, or the internals
Software, Inc.
http://www.mhsoftware.com/
Voice: 303 438 9585
-Original Message-
From: Jay Blanchard [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 5:56 AM
To: George Sexton; mysql@lists.mysql.com
Subject: RE: Seriously.. When are we going to get subqueries?!
[snip]
I
[snip]
The issue with timestamp is this:
You can only have one timestamp with a default of the current date.
My app has two fields in one table
Created_datedatetime default now()
Last_update datetime default now()
This doesn't work with timestamp because timestamp doesn't
On Wednesday 08 June 2005 10:57 pm, George Sexton wrote:
1)Why can't I declare a datetime field with DEFAULT NOW()
4.1 has options to default timestamps on update/inserts or both..
Jeff
pgp2pHd6mM2jF.pgp
Description: PGP signature
Jay Blanchard wrote:
[snip]
The issue with timestamp is this:
You can only have one timestamp with a default of the current date.
My app has two fields in one table
Created_datedatetime default now()
Last_update datetime default now()
This doesn't work with timestamp because
On Wed, 8 Jun 2005 21:57:25 -0600
George Sexton [EMAIL PROTECTED] wrote:
I think MySQL has a little ways to go yet before I would
subjectively call it best.
ok.
I posted twice to the list with questions about porting my
application that runs on (SQL Server, Oracle, PostgreSQL, Sybase SQL
[snip]
1)Why can't I declare a datetime field with DEFAULT NOW()
4.1 has options to default timestamps on update/inserts or both..
[/snip]
Cool, I didn't know that. I should have read the docs more closely this
morning.
--
MySQL General Mailing List
For list archives:
On Thu, 09 Jun 2005 14:28:56 +0100
Gordan Bobic [EMAIL PROTECTED] wrote:
My understanding was the timestamp fields were only set when the
record is created. They are not changed when the record is
modified.
http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html
The first TIMESTAMP column in
[snip]
Well, George, you never mentioned that this was your problem. And you
would run into the same problem, given your definition above,
regardless
of database (unless the database product has a hack to account for it,
I
am not aware of any).
Not true. PostgreSQL can do it. If you want the
Jay Blanchard wrote:
[snip]
Well, George, you never mentioned that this was your problem. And you
would run into the same problem, given your definition above,
regardless
of database (unless the database product has a hack to account for it,
I am not aware of any).
Not true. PostgreSQL
[snip]
Not true. Triggers are in the SQL specification. They are a legitimate
feature with specified expected behaviour. A hack is only implementing
function returns as default field values on timestamps, rather than
handling all field types in a unified way and allowing them to be set to
the
[snip]
Well, Oracle, DB2, SQL Server, Access, PostgreSQL, and Sybase SQL
Anywhere
all do this. I looked at my copy of A Guide to The SQL Standard by
Chris
Date. It pretty plainly states that DEFAULT allows niladic (no argument)
functions. Its about time MySQL stopped complaining about things being
-Original Message-
From: Jay Blanchard [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 8:30 AM
To: George Sexton
Cc: mysql@lists.mysql.com
Subject: RE: Seriously.. When are we going to get subqueries?!
If you are
not pleased with MySQL you have some options.
1. Join
[snip]
1. Join the development work.
I tried contributing over at the Tomcat project and really just got
abused
by the team there.
[/snip]
That is unfortunate, but cannot be held against the MySQL team, can it?
[snip]
B. Find a product more suitable to your needs.
My issue is that shops
-Original Message-
From: Jay Blanchard [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 10:34 AM
To: George Sexton; mysql@lists.mysql.com
Subject: RE: Seriously.. When are we going to get subqueries?!
[snip]
1. Join the development work.
I tried contributing over
subqueries due to the indexing issues unless all tables in the query
were static in size and small enough that the performance hit was
negligable. A table that is growing would mean performance would drop
quickly (especially if there were joins between larger tables that could
have used indexes
On Thursday 09 June 2005 11:47 am, George Sexton wrote:
I'm working in that direction. I first posted to the regular mysql list,
and then I posted again to the internals list. I guess the next step is to
talk to the MySQL people.
We answered you I thought.. Whats the issue you dont know?
I'm a little surprised that case-sensitivity is such a big deal. What sort of
programmers randomly vary their capitalization from one occurrence of an
identifier to the next, and wouldn't people who are so non-detail-oriented be
making a lot of typos as well?
--
Keith Ivey [EMAIL PROTECTED]
to the open source community, and subqueries
than you would have found simply by looking on your own.
This is the kind of thread that most people both love and hate --
1) It takes up space in all our mailboxes and time to read it (the hate)
2) It shows what collaboration and putting multiple heads
On 6/9/05, Keith Ivey wrote:
I'm a little surprised that case-sensitivity is such a big deal. What sort of
programmers randomly vary their capitalization from one occurrence of an
identifier to the next
Inconsistencies in the capitalization aren't necessarily introduced by
a programmer.
You obviously don't understand the limitations of timestamps.
Another limitation in MySQL is that you can only have one timestamp column
with a default of CURRENT_TIMESTAMP.
It's not an issue I don't know. It's an issue I'd like to see fixed so that I
can list MySQL as a supported database
If my compiler would validate the SQL Statements and ensure that they were
perfect, then I wouldn't have a problem at all.
However, since no developer tool that I have ever used (and I've used a lot of
different ones) does compile time validation of SQL syntax, that's pretty
much out of the
George L. Sexton wrote:
You obviously don't understand the limitations of timestamps.
You obviously don't understand how ineffective leading with an insult is.
If you're the first person this has bothered, and if the limitations
don't provide inconsistency with a standard -- just with
On Thursday 09 June 2005 12:42, George L. Sexton wrote:
On Thursday 09 June 2005 12:31, you wrote:
George L. Sexton wrote:
You obviously don't understand the limitations of timestamps.
You obviously don't understand how ineffective leading with an insult is.
My mistake.
If you're the
-
From: George L. Sexton [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 2:26 PM
To: mysql@lists.mysql.com
Subject: Re: Seriously.. When are we going to get subqueries?!
You obviously don't understand the limitations of timestamps.
Another limitation in MySQL is that you can only have
[snip]
...minimal level of common decadency...
[/snip]
heh.
I am minimally decadent!
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
On 6/9/05, Roger B.A. Klorese wrote:
If you're the first person this has bothered
He isn't, search the bugbase. (Including reports that are closed
because it is documented, without providing a fix, workaround or even
recategorizing as feauture request.)
and if the limitations don't provide
On 6/9/05, Bartis, Robert M (Bob) wrote:
Its an email alias. You're asking for help from people you don't even know.
You should therefore present your needs clearly and concisely. You should
expect there to be questions. You should expect to not always get timely
information. you should
On Thursday 09 June 2005 01:26 pm, George L. Sexton wrote:
Another limitation in MySQL is that you can only have one timestamp column
with a default of CURRENT_TIMESTAMP.
How many friggin times do I have to say that this is not an issue with 4.1 and
above? Which, BTW, is production mysql..
Jeff Smelser wrote:
On Thursday 09 June 2005 01:26 pm, George L. Sexton wrote:
Another limitation in MySQL is that you can only have one timestamp column
with a default of CURRENT_TIMESTAMP.
How many friggin times do I have to say that this is not an issue with 4.1 and
above? Which, BTW,
.html
The DATETIME, DATE, and TIMESTAMP Types
for MUCH more detail.
-Original Message-
From: Greg Whalin [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 2:54 PM
To: Jeff Smelser
Cc: mysql@lists.mysql.com
Subject: Re: Seriously.. When are we going to get subqueries?!
Jeff Smelser
database manager is supposed to provide all of
the functionality for input, output and storage!
Anyway, what's all this got to do with subqueries?
On Thursday 09 June 2005 20:53, Greg Whalin wrote:
Jeff Smelser wrote:
On Thursday 09 June 2005 01:26 pm, George L. Sexton wrote:
Another limitation
On Wed, 8 Jun 2005 [EMAIL PROTECTED] wrote:
A long time ago when I was doing support for Lotus Notes, I was told that
the customer who 'complains' about legitimate bugs may be the most valuable
type of customer of all. This is because they care enough to vent. Who
knows how many unhappy
You can have any number of timestamp columns, but only one of them can
be set to autoupdate. As of 4.1 you are not limited to this being the
1st one in the table and CURRENT_TIMESTAMP, CURRENT_TIMESTAMP(), or
NOW() can be used in the DEFAULT. Read
On 6/9/05, Martijn Tonies wrote:
http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html
Absolutely brilliant document *g* ...
So now, it makes a difference if it's the first TIMESTAMP column,
if it's running in MaxDB mode, if it has a defaulf of NULL (which will
be silently changed), if it
http://dev.mysql.com/doc/mysql/en/timestamp-4-1.html
Absolutely brilliant document *g* ...
So now, it makes a difference if it's the first TIMESTAMP column,
if it's running in MaxDB mode, if it has a defaulf of NULL (which will
be silently changed), if it has no default, a default of
On 6/9/05, [EMAIL PROTECTED] wrote:
Okay, so I understand the idea about one field being the creation time, and
the other being the last modified time (which a particularly pedantic
application might regard as being one-and-the-same, at time of
first-creation) and so I see you might want to
On Tuesday 07 June 2005 04:22 pm, Kevin Burton wrote:
Subqueries in 4.1 are totally broken. They don't use indexes. They're
evil. We're told we have subqueries but there's no way anyone on earth
could use them. To make matters worse a lot of developers are TRICKED
into using them
In the last episode (Jun 08), Jeff Smelser said:
On Tuesday 07 June 2005 04:22 pm, Kevin Burton wrote:
Subqueries in 4.1 are totally broken. They don't use indexes.
They're evil. We're told we have subqueries but there's no way
anyone on earth could use them. To make matters worse a lot
On Wednesday 08 June 2005 10:56 am, you wrote:
In the last episode (Jun 08), Jeff Smelser said:
On Tuesday 07 June 2005 04:22 pm, Kevin Burton wrote:
Subqueries in 4.1 are totally broken. They don't use indexes.
They're evil. We're told we have subqueries but there's no way
anyone
[snip]
Thats funny.. looks like it will be added to 5.1.. Dunno why they think
fixing
it is adding a feature..
[/snip]
The best open-source database on the market today? Free
Constant improvements to database? Free
Ability to complain when we don't get what we want? Priceless
--
MySQL General
we don't get what we want? Priceless
First,
*I* wasnt requesting anything.. So you need to reply to the person who was
complaining in the first place. I just thought it was funny.. Them fixing has
no care in the world in my mind since I never use subqueries..
So take your comments elsewhere
when we don't get what we want? Priceless
First,
*I* wasnt requesting anything.. So you need to reply to the person who
was
complaining in the first place. I just thought it was funny.. Them
fixing has
no care in the world in my mind since I never use subqueries..
So take your comments
[snip]
Thats funny.. looks like it will be added to 5.1.. Dunno why they think
fixing
it is adding a feature..
[/snip]
The best open-source database on the market today? Free
Constant improvements to database? Free
Ability to complain when we don't get what we want? Priceless
MySQL
On Wednesday 08 June 2005 11:49 am, you wrote:
Easy there boss, I was just responding to the thread and meant no
offense. I saw the whole thing as funny.
Oh.. email sucks that way..
My apologies as well..
Jeff
pgpvHgJLsGjaw.pgp
Description: PGP signature
Ability to complain when we don't get what we want? Priceless
First,
*I* wasnt requesting anything.. So you need to reply to the person who
was
complaining in the first place. I just thought it was funny.. Them
fixing has
no care in the world in my mind since I never use subqueries
[snip]
I personally find the idea that just because a product is free that
people are not allowed to...
[/snip]
I was just trying to fling a little humor on to the situation, not start
a flame war about who is right and what rights they do or do not have. I
too believe that criticism, in the
, 2005 1:06 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; mysql@lists.mysql.com
Subject: Re: Seriously.. When are we going to get subqueries?!
Jay Blanchard wrote:
[snip]
On Wednesday 08 June 2005 11:16 am, you wrote:
[snip]
Thats funny.. looks like it will be added to 5.1.. Dunno why
A long time ago when I was doing support for Lotus Notes, I was told that
the customer who 'complains' about legitimate bugs may be the most valuable
type of customer of all. This is because they care enough to vent. Who
knows how many unhappy customers one has if none ever complain? What if
Jeff Smelser wrote:
Thats funny.. looks like it will be added to 5.1.. Dunno why they think fixing
it is adding a feature..
WOW! That's just insane! This seriously has to be fixed in 5.0 or sooner...
The thing is that MySQL has both promised this feature and is claiming
that 5.0 is now
the feature. Its just going to shoot people in
the foot and claiming that you support subqueries isn't actually correct
since they're not usable.
The performance of sub-queries in mysql when used in an IN() clause is
embarassingly slow. They are in most cases, unusable because they do
not use
]
Sent: Wednesday, June 08, 2005 10:16 AM
To: Jeff Smelser; mysql@lists.mysql.com
Subject: RE: Seriously.. When are we going to get subqueries?!
The best open-source database on the market today? Free
Constant improvements to database? Free
Ability to complain when we don't get what we want
OK...
Subqueries in 4.1 are totally broken. They don't use indexes. They're
evil. We're told we have subqueries but there's no way anyone on earth
could use them. To make matters worse a lot of developers are TRICKED
into using them and assume that mysql would do the right thing but its
1 - 100 of 208 matches
Mail list logo
