unsubscribe
-----Original Message-----
From: rhn-users-bounces redhat.com [mailto:rhn-users-bounces redhat.com]
On Behalf Of rhn-users-request redhat.com
Sent: Wednesday, September 06, 2006 11:00 AM
To: rhn-users redhat.com
Subject: rhn-users Digest, Vol 31, Issue 13
Send rhn-users mailing list submissions to
rhn-users redhat.com
To subscribe or unsubscribe via the World Wide Web, visit
htt
ps://www.redhat.com/mailman/listinfo/rhn-users
or, via email, send a message with subject or body 'help'
to
rhn-users-request redhat.com
You can reach the person managing the list at
rhn-users-owner redhat.com
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of rhn-users digest..."
Today's Topics:
1. Mysql query return different result after upgrade
to Mysql
4.1.20 (Agustiyanto, Pujo)
2. Re: The purpose of this mailing list (Andy
Purkiss-Trew)
3. Re: Re: The purpose of this mailing list (jef e)
------------------------------------------------------------
----------
Message: 1
Date: Tue, 5 Sep 2006 18:45:26 -0400
From: "Agustiyanto, Pujo" <pagustiyanto louisberger.com>
Subject: [rhn-users] Mysql query return different result
after upgrade
to Mysql 4.1.20
To: "Red Hat Network Users List"
<rhn-users redhat.com>
Message-ID:
<1C2755768836B6439A0C029F5202F620370EC9 LBG-MAIL-VS01.us.lbgcorp.com>
Content-Type: text/plain; charset="us-ascii"
I just upgrade my mysql to version 4.1.20
but I found that one of my query does not return the same
result as my
older version of mysql.
I do not know if this is a known bug or not, or I just got
my mysql
configuration wrong.
I tried the query against this records
CREATE TABLE `portfolio` (
`record_id` int(11) NOT NULL auto_increment,
`company_id` int(11) NOT NULL default '0',
`FY` int(4) NOT NULL default '0',
`started_mon` int(11) NOT NULL default '0',
`field_name` enum('equity','owned_share') NOT NULL
default 'equity',
`field_value` float NOT NULL default '0',
PRIMARY KEY (`record_id`),
UNIQUE KEY `field_name`
(`field_name`,`company_id`,`FY`,`started_mon`)
);
INSERT INTO `portfolio` VALUES (1, 4, 2006, 1, 'equity',
558000);
INSERT INTO `portfolio` VALUES (2, 4, 2006, 1,
'owned_share', 0.67);
INSERT INTO `portfolio` VALUES (3, 12, 2005, 1,
'owned_share', 0.88);
INSERT INTO `portfolio` VALUES (4, 10, 2005, 1,
'owned_share', 0.5);
INSERT INTO `portfolio` VALUES (5, 6, 2006, 1, 'equity',
6.191e+06);
INSERT INTO `portfolio` VALUES (6, 14, 2005, 1,
'owned_share', 0.67);
INSERT INTO `portfolio` VALUES (7, 6, 2006, 1,
'owned_share', 0.53);
INSERT INTO `portfolio` VALUES (8, 5, 2005, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (9, 8, 2006, 1,
'owned_share', 0.5);
INSERT INTO `portfolio` VALUES (10, 4, 2005, 1, 'equity',
550000);
INSERT INTO `portfolio` VALUES (11, 4, 2005, 1,
'owned_share', 0.45);
INSERT INTO `portfolio` VALUES (12, 12, 2006, 1, 'equity',
2.067e+06);
INSERT INTO `portfolio` VALUES (13, 12, 2005, 1, 'equity',
2e+06);
INSERT INTO `portfolio` VALUES (14, 7, 2005, 1, 'equity',
192000);
INSERT INTO `portfolio` VALUES (15, 7, 2006, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (16, 7, 2005, 1,
'owned_share', 0.55);
INSERT INTO `portfolio` VALUES (17, 6, 2005, 1, 'equity',
6e+06);
INSERT INTO `portfolio` VALUES (18, 6, 2005, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (19, 1, 2000, 1, 'equity',
0);
INSERT INTO `portfolio` VALUES (20, 1, 2000, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (21, 9, 2006, 1, 'equity',
1.887e+06);
INSERT INTO `portfolio` VALUES (22, 9, 2005, 1, 'equity',
1.8e+06);
INSERT INTO `portfolio` VALUES (23, 9, 2006, 1,
'owned_share', 0.5);
INSERT INTO `portfolio` VALUES (24, 9, 2005, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (25, 11, 2006, 1, 'equity',
1.3161e+07);
INSERT INTO `portfolio` VALUES (26, 11, 2005, 1, 'equity',
1.3e+07);
INSERT INTO `portfolio` VALUES (27, 11, 2006, 1,
'owned_share', 0.495);
INSERT INTO `portfolio` VALUES (28, 11, 2005, 1,
'owned_share', 0.49);
INSERT INTO `portfolio` VALUES (29, 14, 2004, 1, 'equity',
125000);
INSERT INTO `portfolio` VALUES (30, 8, 2005, 1, 'equity',
3.283e+06);
INSERT INTO `portfolio` VALUES (31, 8, 2005, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (32, 13, 2006, 1, 'equity',
6.41806e+07);
INSERT INTO `portfolio` VALUES (33, 13, 2005, 1, 'equity',
5.34342e+07);
INSERT INTO `portfolio` VALUES (34, 13, 2000, 1,
'owned_share', 1);
INSERT INTO `portfolio` VALUES (35, 10, 2006, 1, 'equity',
6.746e+06);
INSERT INTO `portfolio` VALUES (36, 10, 2005, 1, 'equity',
6e+06);
INSERT INTO `portfolio` VALUES (37, 14, 2006, 1,
'owned_share', 0.8);
INSERT INTO `portfolio` VALUES (38, 7, 2007, 1,
'owned_share', 1);
When I try this query in MySQL 4.1.20-log
SELECT FY, company_id, field_value
FROM portfolio
WHERE field_name = 'owned_share'
AND (
FY, company_id
)
IN (
SELECT max( FY ) , company_id
FROM portfolio
WHERE field_name = 'owned_share'
AND FY <=2006
AND company_id
IN ( 4, 5, 6, 8, 12, 13, 14, 7, 9, 10, 11 )
GROUP BY company_id
)
I got this result
FY company_id field_value
2005 6 1
2006 7 1
2006 8 0.5
2006 9 0.5
2005 11 0.49
2006 14 0.8
But when I try this is in MySQL 4.1.11-standard-log
FY company_id field_value
2006 4 0.67
2005 5 1
2006 6 0.53
2006 7 1
2006 8 0.5
2006 9 0.5
2005 10 0.5
2006 11 0.495
2005 12 0.88
2000 13 1
2006 14 0.8
Does anyone has any idea why this is happened?
thanks
------------------------------
Message: 2
Date: Wed, 06 Sep 2006 13:14:11 +0100
From: Andy Purkiss-Trew <a.purkiss mail.cryst.bbk.ac.uk>
Subject: [rhn-users] Re: The purpose of this mailing list
To: rhn-users redhat.com
Message-ID: <1157544851.4272.9.camel ottawa.ws.cryst.bbk.ac.uk>
Content-Type: text/plain
Mirn Duffy wrote:
> 2. Re: The purpose of this mailing list (M?ir?n
Duffy)
> jef e wrote:
> > Mirn Duffy wrote:
> >
> >> How does this sound?:
> >>
> >> "Discussions about using Red Hat Network
to apply updates to Red
Hat
> >> Enterprise Linux, including discussion about
particular Red Hat
> >> Enterprise Linux updates."
> >>
> >> Is this too broad? How do / have you found
this list most useful?
Let's
> >> focus the purpose towards that.
> >
> > I think it's a good start, but despite all good
intentions to make
the
> > description as accurate as possible, I think that
you might need to
> > actually include what the list *isn't* for.
> >
> > Perhaps also include pointers to the other lists,
so that those
folks
> > that do need help can get better results from the
proper community
of
> > users.
>
> Okay, so I've updated some of the metadata about this
list. The
changes
> I made are listed below.
>
> If there are any corrections for these or any further
suggestions on
how
> to manage this list and better the signal-to-noise
ratio please let me
know.
>
> Thanks,
> ~m
>
> Changes
>
> - The listinfo page [1] has been updated to include a
more descriptive
> about message, including a statement about what this
list is *not* for
> (RHEL-specific topics that don't involve RHN) and
pointers to related
> mailing lists.
>
> - The short description for this list displayed on the
full RH mailing
> list page [2] has been changed to: "Discussions
about Red Hat Network
> (rhn.redhat.com)'
>
> - The following has been added to the welcome message
for new
subscribers:
>
> "Welcome to the Red Hat Network Users list!
>
> This list is for discussions about using Red Hat
Network
> (http://rhn.redhat.com/) to
manage and apply updates to Red Hat
> Enterprise Linux, including discussion about particular
Red Hat
> Enterprise Linux updates.
>
> This list is not intended for discussion about topics
specific to Red
> Hat Enterprise Linux that do not involve Red Hat
Network. For
discussion
> of such topics, you may want to try:
>
> [1] RHEL 4 Discussion -
h
ttps://www.redhat.com/mailman/listinfo/nahant-list
> [2] RHEL 3 Discussion -
h
ttps://www.redhat.com/mailman/listinfo/taroon-list
> [3] Red Hat System Administrators' list:
> https://www.redhat.com/mailman/listinfo/redhat-sysad
min-list"
>
> References
>
> [1] htt
ps://www.redhat.com/mailman/listinfo/rhn-users
> [2] https://www.
redhat.com/mailman/listinfo/
>
In addition, could I suggest the e-mail to new subscribers
(or a
modified version) is also posted to the list on a regular
basis (say the
first of the month), as a reminder to subscribers. I have
seen this
procedure work well on other lists, and the message is easy
enough to
filter out for regulars.
And could we also have some more regular input from Redhat
employees to
keep the list on topic, rather than relying on external
people trying to
do the job.
Andy Purkiss-Trew
------------------------------
Message: 3
Date: Wed, 06 Sep 2006 09:14:59 -0400
From: jef e <jef_umd umd.umich.edu>
Subject: Re: [rhn-users] Re: The purpose of this mailing
list
To: "Discussions about Red Hat Network
(rhn.redhat.com)"
<rhn-users redhat.com>
Message-ID: <44FEC9D3.8040603 umd.umich.edu>
Content-Type: text/plain; charset=ISO-8859-1
Thanks for the changes, Mairmn. We really appreciate the
attempt to get
things on track for the list!
Andy Purkiss-Trew wrote:
> And could we also have some more regular input from
Redhat employees
to
> keep the list on topic, rather than relying on external
people trying
to
> do the job.
I think that this would do the most good for helping to keep
things on
track. A gentle reminder from someone official could work
wonders to
stop the "Who made you king of the list" flame
wars that often break
out.
Thanks again,
jef
------------------------------
_______________________________________________
rhn-users mailing list
rhn-users redhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users
End of rhn-users Digest, Vol 31, Issue 13
*****************************************
_______________________________________________
rhn-users mailing list
rhn-users redhat.com
htt
ps://www.redhat.com/mailman/listinfo/rhn-users
|