dbTalk Databases Forums  

string sort

Go Back dbTalk Databases Forums Databases comp.databases.pick string sort

comp.databases.pick comp.databases.pick


Discuss string sort in the comp.databases.pick forum.



Reply
Page 9 of 9 < 1 2 3 4 5 6 7 8 9
 
Thread Tools Display Modes
  #81  
Old   
Tony Gravagno
 
Posts: n/a

Default Re: string sort - 10-17-2008 , 06:04 PM





There are occasionally questions in the U2 forum about why something
like Part# "95-16A" displays after something like "97-32B". The
answer is that internally the variables are processed into numerics
for the sort (resulting in values of 79 and 65 respectively), and to
avoid that you need to do something like this:
IF "X":PART1 > "X":PART2 THEN ...
Just yesterday someone asked why a string (part#?) like "2E-29" passed
a NUM(x) test, and the answer is that it's recognized as scientific
notation.

I discuss a related situation in my blog:
"D3 Precision - Who says MV doesn’t have data types?"
removeNebula-RnD.com/blog/tech/mv/2008/08/d3precision1.html

Right? Wrong? It's academic. It just "is". All platforms are
different. Test test test...

The advantage we have in participating in these forums is that we
learn more about exactly which areas are more prone to cross-platform
issues like this.

T


"Chandru Murthi" wrote:

Quote:
If "traditional" Pick systems work one way and UniData works another, it;s
Unidata that's "wrong". The result above is weird.

Chandru

(A1 = 0) < (HH1=0) < (ZZZZ1=0) ...

Lower values of zero sort higher than higher values of zero. ;0


Reply With Quote
  #82  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM





On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #83  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #84  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #85  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #86  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #87  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #88  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
  #89  
Old   
Bill_H
 
Posts: n/a

Default Re: string sort - 10-18-2008 , 03:15 PM


On UniData you may want to play with SORT.TYPE and UDT.OPTIONS. I set
SORT.TYPE = 2 and UDT.OPTIONS 69 OFF. This makes sure right-justified
alpha-numeric data is sorted properly like PICK. There is a BUG in
UniData where if UTD.OPTIONS 69 is set and SORT.TYPE is non-zero then
UniQuery doesn't use indexes when selecting (sorting).

HTH,

Bill


frosty wrote on 10/17/2008 9:07 AM:
Quote:
Could be. I'm on UniData. Don't know from MVBase,
but have seen problems with 'AR' on UniData. For
example, your code produces this:

A1]A6]F6]HH1]Q68]A123]HH12]AA678]FDQ88

Reply With Quote
Reply
Page 9 of 9 < 1 2 3 4 5 6 7 8 9

« Previous Thread | Next Thread »



Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.


Contact Us - dbTalk Databases Forums - Archive - Top