Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Character size limit

2 posts in DataWindow Last posting was on 2008-06-12 00:48:57.0Z
Jacqueline Posted on 2008-06-11 22:39:39.0Z
From: "Jacqueline" <jacqueline.mcmullan@medtronic.com>
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Character size limit
Lines: 23
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4850542b@forums-1-dub>
Date: 11 Jun 2008 15:39:39 -0700
X-Trace: forums-1-dub 1213223979 10.22.241.152 (11 Jun 2008 15:39:39 -0700)
X-Original-Trace: 11 Jun 2008 15:39:39 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87152
Article PK: 416409

Environment: PB 10.2.1 Build 9004, Oracle 9i

Scenerio: datawindow is dynamicly changed based on user selection using
DataWindow.Table.Select (Modify function). Sometimes a agrument choosen
(its value) by the user could be Case Sensitive. User's have an option of
asking for Case Senitive agruments for there agruments. For example, fname
= 'Kimberly' (1st character is capital, however, 2nd character and beyond
are lower case). In fact, could be a combination of lower and upper cases,
but the agrument must be exact.

We give the user this flexiblity, when you take a look at the sql either way
(Case or Not Case Sensitive) the Not option hanges and does not return an
error. However, if you run this same query (both options) in TOAD they both
return, jncluding the Not option which is using upper() function. In fact,
the Not option returns slower because of the extra conversion of upper() for
the column and the agruement.

Does anyone know why this is happening? Is there a character limit, if so
what is that limit?

Thanks in advance


Jim Madderra Posted on 2008-06-12 00:48:57.0Z
From: "Jim Madderra" <jmadderra@astound.net>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <4850542b@forums-1-dub>
Subject: Re: Character size limit
Lines: 32
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48507279$1@forums-1-dub>
Date: 11 Jun 2008 17:48:57 -0700
X-Trace: forums-1-dub 1213231737 10.22.241.152 (11 Jun 2008 17:48:57 -0700)
X-Original-Trace: 11 Jun 2008 17:48:57 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87155
Article PK: 416412

Need to see the SQL to even have a clue. If there is a limit it must be
quite large, because I've created sql dynamically that prints on tons of
pages, with a ridiculous amount of nested selects, etc... My guess is if it
runs in TOAD then it can be 'fixed' to run in PB.....

"Jacqueline" <jacqueline.mcmullan@medtronic.com> wrote in message
news:4850542b@forums-1-dub...
> Environment: PB 10.2.1 Build 9004, Oracle 9i
>
> Scenerio: datawindow is dynamicly changed based on user selection using
> DataWindow.Table.Select (Modify function). Sometimes a agrument choosen
> (its value) by the user could be Case Sensitive. User's have an option of
> asking for Case Senitive agruments for there agruments. For example,
> fname = 'Kimberly' (1st character is capital, however, 2nd character and
> beyond are lower case). In fact, could be a combination of lower and
> upper cases, but the agrument must be exact.
>
> We give the user this flexiblity, when you take a look at the sql either
> way (Case or Not Case Sensitive) the Not option hanges and does not return
> an error. However, if you run this same query (both options) in TOAD they
> both return, jncluding the Not option which is using upper() function. In
> fact, the Not option returns slower because of the extra conversion of
> upper() for the column and the agruement.
>
> Does anyone know why this is happening? Is there a character limit, if so
> what is that limit?
>
> Thanks in advance
>
>