_sequence jumps by total record count through odbc .newval

[freak]

We are accessing progress 9.1d through php and Merant 3.6 odbc on windows xp 32bit. We are trying to get the next-value sequence. Each time we execute something like...

SELECT pub.orderheadseq.currval FROM PUB.orderhead

...the nextval get incremented by the total of all records. Like it is executing nextval for each record which in our case is rougly 300,000 times. Are we doing something wrong with the select statement?

 

[freak]

Sorry that should read...

SELECT pub.orderheadseq.nextval FROM PUB.orderhead

 

[durkadurka]

TRICK IS NEXTVAL ACUALLY RUN FOR NUMBER OF RECORDS RETURNED IN "FROM". YOU CAN TRY

[LEFT][COLOR=#333333]SELECT TOP 1 pub.orderheadseq.nextval FROM PUB.orderhead[/COLOR][/LEFT]

OR EBEN BETTER

SELECT pub.orderheadseq.nextval FROM SYSPROGRESS.SYSCALCTABLE

CUZ THAT TABLE IS SMALL AND HAVE ONLY 1 RECORD!!

 

[freak]

"TOP 1" is not supported.

 

[durkadurka]

AND I ASSUME THAT U TRIDE ALSO

SELECT pub.orderheadseq.nextval FROM SYSPROGRESS.SYSCALCTABLE

MY MAIN MAN???

 

[freak]

Yep... just wanted to point out that TOP 1 is not supported.

 

[Stefan]

"TOP 1" is not supported.

TOP is available as of 10.1B (see prokb).

 

[freak]

TOP is available as of 10.1B (see prokb).

Yes but as I posted, we are on 9.1b.

 

[Cringer]

What I think Stefan is trying to imply, subtly, is that you really should be upgrading. All of Progress v9 is out of date and unsupported. You should be going to v10 or 11 as soon as possible. If you can compile the source then it's an easy step. If you can't then you should be putting pressure on your vendor.

 

[Stefan]

Indeed, my remark was simply to qualify "top 1 is not supported" to "top 1 is not supported on an unsupported progress version", just in case anyone reads this and gets the wrong idea.

 

[durkadurka]

yep... Just wanted to point out that top 1 is not supported.

i thinking you mis-spell "thank you" lol