RE: [cobalt-users] Client for Interbase?

["Todd Kirk" <tkirk@xxxxxxxxxxxxxx>]

>Yes please!
>I'm trying to figure out the Interbase too and was working with IBConsole
as the
>client (Thanks for letting me know not to waste another day with it).  Have
you
>found any good resources?
>
>Jennifer

Advanced apologises for the long post.


Well here is where I am at, there are currently only two ways to connect and
create databases, tables and their datatypes (see below extract), for
Interbase Classic Server beta 6 (which is what is factory standard with
RAQ4r). We are currently getting used to WISQL, currently the only GUI. We
created a test database by using the command line ISQL (part of Interbase as
standard, must be done via telnet, instructions below). Now we are moving to
creating a database with WISQL (the GUI), creating a table and testing an
ASP page. Will post results when that works 100%.

At the moment the command line creation of a user, a database, a table then
creation of an ASP page using the created users login (or sysdba) has worked
fine and the ASP page worked perfectly. Will write back when I get used to
WISQL, if you like.

An extract from Borland website (makers of Interbase)
http://community.borland.com/article/0,1410,26080,00.html
Alert : The IBConsole program currently available for download is
unfortunately a tool designed and developed for use with InterBase 6.0
versions that have implemented the Services API. Currently, that -would
exclude any Classic releases of the InterBase engine, namely the Linux 6.0
Beta Release.
Good News : There are currently two options available to the community for
using the Linux InterBase 6.0 Beta Release.
* The command line tools that ship with both the Linux and Windows 6.0 Beta
Client packages will work with the InterBase Linux 6.0 Beta Server.
* There also exists a powerful tool in the InterBase Community that can and
does address the current need for a Windows graphical interface to the Linux
InterBase 6.0 Server.
Written and offered as freeware by Jason Wharton, IB_WISQL.exe, is a very
complete and useful tool. Jason's IB_WISQL, built with his IBOjects
technology, has tons of great functionality. I personally found the Export,
Datapump and QueryForms features very handy - Markus.

HERE IS HELP TO USE THE COMMAND LINE UTILITY ISQL, received from Easysoft,
the ODBC driver we are currently using on our windows client system.

Ok. The thing to do is to create a new database on the Raq. To do this use
the
isql utility that is part of InterBase, this will be somewhere like
/opt/interbase/bin/isql, find it and run it (as root would be simpliest)

/opt/interbase/bin/isql
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database '/opt/interbase/sample.gdb';
SQL> quit;

This will create a empty database

Then make it readable by anyone

chmod 0666 /opt/interbase/sample.gdb

The you can put /opt/interbase/sample.gdb into the database entry in the Raq
setup page, and try connecting.

That should be pk. Now you need to do the same in the database entry on the
windows machine, but put server: infront of that path, where server is the
name
of your RAQ, or maybe try a IP address, but that is down to your windows
TCP/IP
stack to resolve.

Try connecting, if that fails, it may be because the raq is not listining,
check on the raq (as root) that you have the following in /etc/services

gds_db          3050/tcp  # InterBase Database Remote Protocol

If not add it,

and also in /etc/inetd.conf (all one line)

gds_db  stream  tcp     nowait.30000      root
/opt/interbase/bin/gds_inet_server gds_inet_server # InterBase Database
Remote
Server

If not add it, and restart inetd (find the ip address)

ps aux | grep inetd
root       465  0.0  0.0  1164  252 ?        S    Apr19   0:01 inetd
nick     24735  0.0  0.1  1336  524 pts/1    S    11:21   0:00 grep inetd

kill -HUP 465

Then try again.

Regard,
Todd Kirk