From: <no...@so...> - 2001-08-13 05:56:03
|
Bugs item #450404, was opened at 2001-08-12 22:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=450404&group_id=9028 Category: ISQL Group: Confirmed Bug Status: Open Resolution: None Priority: 5 Submitted By: Claudio Valderrama C. (robocop) Assigned to: Nobody/Anonymous (nobody) Summary: isql uppercases role in the command line Initial Comment: I think example should be enough clear: when isql is invoked and the role is passed in the command line, it always uppercases the role: H:\ibdev\fbbuild\interbase\dsql>isql c:/proy/fbtest.gdb -u cvc -p pw -r "for cvc" Database: c:/proy/fbtest.gdb, User: cvc, Role: FOR CVC SQL> As you can see, isql puts the message with the role in uppercase and indeed the engine received it uppercased. Notice that double quotes weren't interpreted as "don't change the input parameter". However, when doing the connection as a command, the role is processed correctly: H:\ibdev\fbbuild\interbase\dsql>isql Use CONNECT or CREATE DATABASE to specify a database SQL> connect c:/proy/fbtest.gdb user cvc password pw role "for cvc"; Database: c:/proy/fbtest.gdb, User: cvc, Role: for cvc SQL> Now, isql reflects the unchanged role and the engine receives it correctly. Whether this anomaly exists for some purpose I don't know, but I consider it a bug. Both ways to work with isql should be equivalent when facing identifiers surrounded by double quotes. C. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=450404&group_id=9028 |