karen_denise@... wrote:

> Following the Quick Start Guide's instructions on pg. 26, I typed the following into isql:

>

SQL>> connect xnet://employee user sysdba password mynewpassword;

> And it responded, thus:


> Statement failed, SQLSTATE = 08006
> Unable to complete network request to host "xnet".
> -Failed to establish a connection.

The QSG may need some correction if it is offering that exact string
as an example. Missing here is a hostname, viz.

INET://machost:employee user sysdba password mynewpassword;

Depending on your network configuration, or if you don't know your
Mac's network name, you could do

INET://localhost:employee user sysdba password mynewpassword;

or, more simply:

localhost:employee user sysdba password mynewpassword;

> What should I be doing differently?

For an embedded ("hostless") connection using the syntax you chose,
you need an extra forward slash in the string:

connect inet:///employee user sysdba password mynewpassword;

But you can do the same thing without that extra layer and you won't
need the password:

connect employee user sysdba;

> I am on a Mac, if that makes a difference.

It doesn't, provided you have taken care of the filesystem
permissions.
----------------------------------------

Quoting from another of your posts:

> My reason for attempting to use Firebird is that LO is transitioning
> to an embedded Firebird database, which is still, as I understand,
> fairly buggy. A knowledgable person on their forum suggested I try
> the Firebird 3 Server.

OK, the "buggy" thing would be the Firebird driver and interface that
is under development by some LO guys and a Firebird guy, Marius Popa.
Firebird Embedded itself is simply one of several "server modes"
available for deploying Firebird. It's not something special that has
been churned out specifically for Libre Office.

Perhaps I can help you to position yourself in some kind of developer
spectrum by explaining a little about the structure of a database
application.

At the top level is the client application, typically written in a
computer language such as C++, ObjectPascal, C#, Java.

At the next level is a language-specific driver. This layer acts as a
"translator" between the language of the client application and the
application programming interface (API). This layer lives on the
client machine. On a Mac, its name is fbclient.dylib. You will find
a copy of it in your /bin directory. For some languages, such as Java
or the .NET languages, this layer is not loaded dynamically but it
coded natively in the driver layer.

Right at the back-end - on the server that hosts Firebird - is the
Firebird Server, which can be configured to accept either network
connections or embedded connections or both. Embedded connections are
possible only from the same machine where the Firebird server and the
databases are located.

LO Base is a client application. The transition project is to use the
Firebird server in embedded mode: I doubt there is a plan to use LO
Base as a remote client - but I really do not know!

So, essentially, the LO model is a local client application intended
to give you an interface through which you can create and work with
Firebird databases in embedded mode. I don't know anything about the
design details but it seems you are expecting that it will give you
some kind of interface that avoids your having to know anything about
databases, nor how to write database applications, in order to create
and maintain database objects. If so, it seems to me that by going the
route you are going, you are showing great courage!

To get "with it" and stick with it, it seems you might have some work
to do to get down and dirty and get your head around the file systems,
user/group permissions, network configurations and text editors, along
with the bash shell and some system tools at the command-line level.

Helen






---
This email has been checked for viruses by AVG.
https://www.avg.com