On Sun, 2003-09-28 at 17:54, Dr. Ralf Czekalla wrote: > Hi Hermann, > > Hermann Himmelbauer wrote: > > >On Saturday 27 September 2003 11:56, jean-michel OLTRA wrote: > > > > > >>Le vendredi 26 septembre 2003, Philippe a �crit... > >> bonjour, > >> > >> > >>>Is there a way to execute a SELECT statement with a command line tool. > >>>I've tried with "loadercli". It answered me that everything was "OK", but > >>>there was no output data... (I excepted the result of my SELECT query to > >>>appear on the screen in a text format...). > >>> > >>> > >>I use dbmcli which can call select statements and get result, but not > >>get any resultset whith a dbproc call (but ok !) > >>syntax: > >>dbmcli -d database -u dbm,dbmpasswd -uSQL user,passwd -c "sql_execute stmt" > >> > >> > > > >Well, probably this works - but I was told, that using dbmcli for everyday SQL > >usage should not be used by a SAPDB developer (Daniel Dittmar). Here is my > >question and his response: > > > > > > from my point of view this is completely OK !!! > > As long as there is no other tool > > - xquery was discontinued > - xsql is not able to work remotely and isn't such adaptive than dbmcli > > I also use dbmcli to get fast infos out of the database and I also use > it in batches !!
No, there are other tools. The dbm protocol is clearly not suited for sql. For exemple if you use a unicode database, dbmcli sends a blank string for every varchar in your database. The preferred ways for sql interrogation should be : - ODBC, which is pretty easy to set up on a unix/linux system - Any JDBC query tool if you are using a unicode database (squirrel sql for example) Advocating for dbmcli sql processing is clearly not the way to go. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
