Re: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
Looking at the SQL Anywhere Documentation I only saw control of escapes in the INPUT statement. When I looked for Escapes in the documentation all I found was the INPUT statement which does allow the...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
The trace looks like this indeed without bind variables they include the text in single quotes PB126 192c-2584ENTER SQLExecDirectW HSTMT 0x01D41540WCHAR *...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
It's not stonewalling, or a bug, it's documented behavior that does not meet your needs. The behavior of DisableBind=1 with respect to string values inserted via DataWindow is described with an...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
Thanks Breck What is documented in SQL Anywhere is the behavior of literal strings, what is documented in Powerbuilder is the effect of disable bind on defaults. Nowhere does it say that if if you are...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
It's too bad that PowerBuilder REPLACE doesn't work like SQL Anywhere's version (which does a search-and-replace of all occurrences of a substring). If it existed, you could use it to replace all...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
We have a lot of functionality on our library - and could adapt the global replace function to do this - but we would have to write a service that we would install in our ancestor class datawindow that...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
I think prepared statements and bind variables make things go faster, otherwise why bother? I don't know of any tools for translating rich text to standard text, but they must exist since Windows...
View ArticleRe: SQL Anywhere and DisableBind=1, An Open Manhole Cover?
I think our original problem with bind variables had something to do with inserts on very large (column wise) tables and overwhelming the SQL buffer... That's the area which is foremost in my mind...
View ArticleNewbie: No "dbserv" in SQL Anywhere 17 Installation
Hello all, First, thank you in advance for your help. I recently purchased SAP SQL Anywhere 17 and I'm having trouble. I should mention that I am not a database expert or programmer. I only need to...
View ArticleRe: Newbie: No "dbserv" in SQL Anywhere 17 Installation
Sounds like you have done everything correct from the SQL Anywhere perspective. There is no file with the name "dbserv" in the product and there has never been. I wonder if that is just a stand-in...
View ArticleEvaluate date field, use only if not null/empty in query.
We have this query: select LastReqTime,BlockedOn,UncommitOpsFROM sa_conn_info()WHERE LastReqTime < DATEADD(mi,-60,GETDATE()) AND BlockedON > 0 AND UncommitOps = 0 Normal data example would be...
View ArticleClik here to view.
Re: Newbie: No "dbserv" in SQL Anywhere 17 Installation
Hi Nick, Thank you very much for your response! You are absolutely correct and I apologize for the error I made in my initial posting. The file I am looking for (and which is missing from the...
View ArticleRe: Newbie: No "dbserv" in SQL Anywhere 17 Installation
Hi Thomas, License key you enter during installation determines which components are installed. And it appears the key used does not have network server (dbsrv17) component. Do you have any .lic in...
View ArticleRe: Newbie: No "dbserv" in SQL Anywhere 17 Installation
Hi Jinwoo, Thank you for your reply! I requested a permanent license key from SAP in their portal and then uninstalled and reinstalled SQL Anywhere 17 using the new key. It worked! the bin64 folder...
View ArticleRe: Evaluate date field, use only if not null/empty in query.
Hi John, Unfortunately, I don't fully understand your issue.So I talk based on my guess. ISDATE function tests if a string argument can be converted to a date (/datetime). You can rewrite the query as...
View ArticleRe: Evaluate date field, use only if not null/empty in query.
Hi John, I wonder if you could try add 'LastReqTime is not null', like this: select LastReqTime,BlockedOn,UncommitOpsFROM sa_conn_info()WHERE LastReqTime is not null and LastReqTime <...
View ArticleRe: JDBC Connection to SQLAnywhere 11.0.1
Hi Tim, I was wondering if you could try this: Connection con = DriverManager.getConnection("jdbc:ianywhere:driver=SQL Anywhere...
View ArticleRe: Evaluate date field, use only if not null/empty in query.
Hi John, I guess your problem is that things aren't the way we might intuitively expect them to be.While LastReqTime looks like a datetime, it technically is a varchar (255) as you'll see in the...
View ArticleRe: Evaluate date field, use only if not null/empty in query.
Hi Kiochi.Thank you for your response. I guess I should have explained a bit more when I posted.The main problem I had was that null values in LastReqTime were causing a "cannot convert"error when the...
View ArticleRe: Evaluate date field, use only if not null/empty in query.
Volker,That explains quite a bit. I've done extensive programming and scripting, but this is my first foray into SQL queries. The logic and construct is different from what I know, and unfortunately I...
View Article