Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
AW: "order by " problem with 7.6.00.34

AW: "order by " problem with 7.6.00.34

2007-02-14       - By H?bschen, Peter

 Back
Reply:     1     2  

> -- --Urspr?ngliche Nachricht-- --
> Von: Robert Klemme [mailto:shortcutter@(protected)]
> Gesendet: Dienstag, 13. Februar 2007 22:51
> An: H?bschen, Peter
> Cc: maxdb@(protected)
> Betreff: Re: "order by" problem with 7.6.00.34
>
> 2007/2/13, H?bschen, Peter <Peter.Huebschen@(protected)>:
> > Hello,
> >
> > I have a strange problem with an "order by"-clause, which
> doesn't sort as expected. First it appeared in a stored
> procedure which works correctly with SAPDB 7.4 on Linux. For
> testing I created a local MaxDB-Installation on my PC (WinXP
> Pro.) with MaxDB 7.6.00.34 and imported a current backup from
> my 7.4. database. The "order by" clause looks a little bit
> "strange", but due to an old design failure I had to go this way.
> > Here's the Select-Statement:
> >
> > SELECT tbl_Anfrage.Anfragenummer,
> >        tblKunden.Kundenname
> > FROM tblKunden,
> >      tbl_Anfrage,
> >      tbl_Teile
> > WHERE tblKunden.Kunden_ID (+) = tbl_Anfrage.Kunden_ID
> >     AND tbl_Anfrage.lfd_Anfragenummer =
> tbl_Teile.lfd_Anfragenummer (+)
> >     AND tbl_Anfrage.Anfragenummer Like 'D-%/07'
> > GROUP BY tbl_Anfrage.Anfragenummer,
> >          tblKunden.Kundenname,
> >          tbl_Anfrage.Anlagedatum
> > ORDER BY
> >
> SUBSTR(Anfragenummer,1,2)||substr(Anfragenummer,6,2)||'0'||substr(Anfr
> > agenummer,3,2) desc
> >
> > The output looks like this:
> > D-01/07  XYZ
> > D-03/07  ABC
> > D-05/07  EFG
> > D-02/07  HIJ
> > D-06/07  MNO
> > D-04/07  STV
> >
> > correctly it should be:
> > D-06/07  MNO
> > D-05/07  EFG
> > D-04/07  STV
> > D-03/07  ABC
> > D-02/07  HIJ
> > D-01/07  XYZ
> >
> > If I add
> >
> SUBSTR(Anfragenummer,1,2)||substr(Anfragenummer,6,2)||'0'||substr(Anfr
> > agenummer,3,2) so it is displayed in the result and in the group by
> > clause, it is ordered correctly, but I get some duplicate rows of
> > D-01/07. So I don't know where the problem is and I found
> nothing in
> > the documenation
>
> One strange thing: you group by a tbl_Anfrage.Anlagedatum but
> do not show it anywhere. This might be responsible for
> duplicates although I fail to understand how then you don't
> see the duplicates in your original query (i.e. the one where
> you did not add the SUBSTR...).
>
> Did you check the bugtracker?  Maybe this is a known issue.
> If not I'd probably try to recreate a simple test case and
> submit it as a bug report. I know that in the past there were
> issues with joins.  So one thing to try could be to change
> the DB parameter that controls join execution.  For me that
> helped in one case in the past (7.5).
>
> Good luck!
>
> robert
>

Hello,

I've checked it an "Anlagedatum" is just an old thing. I've deleted it and I
got the same results.
I've also checked bugtracker, which I didn't know earlier, but found nothing
appropriate.

Which DB parameter did you change?

Kind regards
Peter

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)