1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Configuring</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.73.2">
<link rel="start" href="index.html" title="GNOME Data Access manual">
<link rel="up" href="installation.html" title="Installation">
<link rel="prev" href="compiling.html" title="Compiling with the library">
<link rel="next" href="connecting.html" title="Beginning">
<meta name="generator" content="GTK-Doc V1.10 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
<link rel="chapter" href="introduction.html" title="Introduction">
<link rel="chapter" href="architecture.html" title="libgda architecture">
<link rel="chapter" href="installation.html" title="Installation">
<link rel="chapter" href="connecting.html" title="Beginning">
<link rel="chapter" href="processing-queries.html" title="Processing queries">
<link rel="chapter" href="ch06.html" title="Transactions and batch processes">
<link rel="chapter" href="managing-errors.html" title="Managing errors">
<link rel="chapter" href="main_example.html" title="Full example">
<link rel="chapter" href="migration.html" title="Some formulae for migration from old version">
<link rel="chapter" href="libgda-api.html" title="Client API Reference">
<link rel="chapter" href="libgda-providers.html" title="GDA Providers">
<link rel="chapter" href="libgda-xql.html" title="XML Queries">
<link rel="chapter" href="libgda-reports.html" title="GDA Report Engine">
<link rel="appendix" href="fdl.html" title="Appendix A. GNU Free Documentation License">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2"><tr valign="middle">
<td><a accesskey="p" href="compiling.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
<td><a accesskey="u" href="installation.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
<th width="100%" align="center">GNOME Data Access manual</th>
<td><a accesskey="n" href="connecting.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
</tr></table>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="installation-configuring"></a>Configuring</h2></div></div></div>
<p>
Depending on the use you're going to get out of <span class="application">libgda</span>, you may have
to dig deep into its internals, but don't be afraid, things have been
implemented to be easy to use.
</p>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="installation-development"></a>Configuration for development</h3></div></div></div>
<p>
If you want to develop applications using <span class="application">libgda</span>, you should
install the libgda-dev[el] package if you do a <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=RPM"><span class="acronym">RPM</span></a> or <a class="link" href="installation-installing.html#installation-debian" title="Debian installation">Debian-based</a>
installation. If you compiled the source code, development files are
installed in your system.
</p>
<p>
The only step you need to do to make sure everything is well
installed, is to check that <span class="application">libgda</span> libraries and binaries are seen
by your system. That is, make sure that the <span class="application">libgda</span>
<code class="filename">bin/</code> directory is in your
<code class="envar">PATH</code> environment variable, as well as the
<code class="filename">lib/</code> in your
<code class="envar">LD_LIBRARY_PATH</code> (or
<code class="filename">/etc/ld.so.conf</code> file).
</p>
<p>
You have to include a headers file, and it is:
</p>
<pre class="programlisting">
#include <libgda/libgda.h>
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="installation-client"></a>Configuration for accessing a database</h3></div></div></div>
<p>
If you want to access a data source through a <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a>
provider, you must first of all have access to this provider, and
most importantly, this provider should have access to its specific
data source. So, first have your database up and running.
For this, you'll have to check your specific data source
documentation, or see the <span class="application">libgda</span> providers' specific documentation.
</p>
<p>
Once you've got your <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> provider installed,
whether on your machine or on another one on the network, you must
configure your local system to have access to it. If you're on a
local installation, once you have installed the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> provider (by
compiling it or by installing its <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=RPM"><span class="acronym">RPM</span></a> or Debian package), the
provider is visible in your machine. This is because the provider
installs itself in a well known location that makes <span class="application">libgda</span>
itself know about the new provider.
</p>
<p>
Then, the next step is to configure the data sources you want
available on your system. For doing this, you should, as for now, use
<span class="application">GNOME-DB</span>, which is a front-end to <span class="application">libgda</span> for the
<a class="ulink" href="http://www.gnome.org" target="_top">GNOME project</a>.
<sup>[<a name="id445510" href="#ftn.id445510" class="footnote">1</a>]</sup>
</p>
<p>
Command-line tools will be provided in <span class="application">libgda</span> for doing so in a
not-too-distant future, so you may want to know what information
you need to setup a data source.
</p>
<p>
One of the problem <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> solves is the naming of
data sources. Every database system has it's own way of defining
names for it's databases. For example <span class="application">MySQL</span> uses the hostname,
port number, and the name of the database. Other databases, like
Solid use the hostname and port number only. There is no support
for multiple databases per server. Because the client does not
need all these details, the <span class="application">libgda</span> configuration defines all the
properties of such a data source, so that the correct data base
server can be contacted. This information is accessed by the
client library and sent to the provider, which in turn will parse
the string to decide which database must be connected to. The
data stored for each data source is as follows:
</p>
<div class="programlistingco">
<pre class="programlisting">
[sales]
Provider=MySQL
DSN=DATABASE=test;HOST=localhost;PORT=1111
Description=MySQL Test Database in native mode
Username=username
Password=password
</pre>
<div class="calloutlist"><table border="0" summary="Callout list">
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/1.png" alt="1" border="0"></p></td>
<td valign="top" align="left"><p>
The provider for this database is the gda-mysql
provider. The value of this entry is used as the
object ID for the plug-in activation.
</p></td>
</tr>
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/2.png" alt="2" border="0"></p></td>
<td valign="top" align="left">
<p>
This is the most important entry. The value of
this entry is the string sent to the provider so
that it knows which datasource to access. How this
entry is interpreted by the providers is described
in the provider section.
</p>
<p>
There are, though, a set of default properties that can
be used for the connection string for all providers. Those
are:
</p>
<div class="itemizedlist"><ul type="disc">
<li><p>USERNAME: user name to be used for authentication.</p></li>
<li><p>PASSWORD: password to be used for authentication.</p></li>
</ul></div>
<p>
</p>
</td>
</tr>
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/3.png" alt="3" border="0"></p></td>
<td valign="top" align="left"><p>
The value of this entry is a short description of
the datasource. It is here for convenience only
and it is not used for any purpose.
</p></td>
</tr>
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/4.png" alt="4" border="0"></p></td>
<td valign="top" align="left"><p>
The user name to be used when connecting to the database.
</p></td>
</tr>
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/5.png" alt="5" border="0"></p></td>
<td valign="top" align="left"><p>
The password to be used when connecting to the database.
This is stored in plain text, so be sure you restrict access
to the configuration file (<code class="filename">~/.libgda/config</code>)
to any "dangerous" users.
</p></td>
</tr>
</table></div>
</div>
<p>
</p>
<p>
The <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=XML"><span class="acronym">XML</span></a> configuration file (<code class="filename">~/.libgda/config</code>) is not
recommended to be modified by hand and, for our example, it is
something like this:
</p>
<pre class="programlisting">
<?xml version="1.0"?>
<libgda-config>
<section path="/apps/libgda/Datasources/sales">
<entry name="DSN" type="string" value="PORT=1111;DATABASE=test;HOST=localhost"/>
<entry name="Description" type="string" value="MySQL Test Database in native mode"/>
<entry name="Password" type="string" value="password"/>
<entry name="Provider" type="string" value="MySQL"/>
<entry name="Username" type="string" value="username"/>
</section>
</libgda-config>
</pre>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="data-sources-API-functions"></a>Managing data sources with API functions</h4></div></div></div>
<div class="sect4" lang="en">
<div class="titlepage"><div><div><h5 class="title">
<a name="id445733"></a>Create data sources</h5></div></div></div>
<p>
To create a data source you must use the function <a class="link" href="libgda-gda-config.html#gda-config-save-data-source" title="gda_config_save_data_source ()"><span class="emphasis"><em>gda-config-save-data-source ()
</em></span></a>
</p>
<p>
Here you see how to create a data source named
<span class="emphasis"><em>foo_ds</em></span>. If you do not need to give an username or password to
enter the database, you could put <span class="emphasis"><em>NULL</em></span>.
</p>
<pre class="programlisting">
gda_config_save_data_source ("foo_ds", "PostgreSQL", "DATABASE=foo_db",
"description of foo_ds", "foo_username", "foo_password");
gda_config_save_data_source ("other_foo_ds", "MySQL", "DATABASE=other_foo_db,HOST=db.foo.com",
"description of other_foo_ds", "foo", NULL);
</pre>
<p>
For more details about provider specific information see in the section about
<a class="link" href="installation-configuring.html#installation-provider" title="Provider's specific information">providers specific information</a>.
</p>
<p>
There was a little bug<sup>[<a name="id445780" href="#ftn.id445780" class="footnote">2</a>]</sup>, and it
is that <a class="link" href="libgda-gda-config.html#gda-config-save-data-source" title="gda_config_save_data_source ()">gda_config_save_data_source()</a>
does not create the configuration directory <code class="filename">~/.libgda</code>, so you have to do
it.
</p>
<p>
There is no problem about calling several times to this
function because if you save an existing data source, it
is replaced.
</p>
</div>
<div class="sect4" lang="en">
<div class="titlepage"><div><div><h5 class="title">
<a name="id445805"></a>Removing data sources</h5></div></div></div>
<p>
To remove a data source you must use the function <a class="link" href="libgda-gda-config.html#gda-config-remove-data-source" title="gda_config_remove_data_source ()"><span class="emphasis"><em>gda-config-remove-data-source ()
</em></span></a>
</p>
<p>
Here you see how to remove a data source named
<span class="emphasis"><em>foo_ds</em></span>.
</p>
<pre class="programlisting">
gda_config_remove_data_source("foo_ds");
</pre>
</div>
<div class="sect4" lang="en">
<div class="titlepage"><div><div><h5 class="title">
<a name="id445835"></a>Listing available data sources</h5></div></div></div>
<p>
To list available data sources you must use the function <a class="link" href="libgda-gda-config.html#gda-config-get-data-source-list" title="gda_config_get_data_source_list ()"><span class="emphasis"><em>gda_config_get_data_source_list ()
</em></span></a>
</p>
<p>
Here you see a function which lists the available data sources.
</p>
<div class="programlistingco">
<pre class="programlisting">
void
list_datasources (void)
{
GList *ds_list;
GList *node;
GdaDataSourceInfo *info;
ds_list = gda_config_get_data_source_list ();
g_print ("\n");
for (node = g_list_first (ds_list); node != NULL; node = g_list_next (node))
{
info = (GdaDataSourceInfo *) node->data;
g_print
("NAME: %s PROVIDER: %s CNC: %s DESC: %s USER: %s PASSWORD: %s\n",
info->name, info->provider, info->cnc_string, info->description,
info->username, info->password);
}
g_print ("\n");
gda_config_free_data_source_list (ds_list);
}
</pre>
<div class="calloutlist"><table border="0" summary="Callout list">
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/1.png" alt="1" border="0"></p></td>
<td valign="top" align="left"><p>Our function.</p></td>
</tr>
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/2.png" alt="2" border="0"></p></td>
<td valign="top" align="left"><p>Note that you must free the list when you finish using it.</p></td>
</tr>
</table></div>
</div>
</div>
<div class="sect4" lang="en">
<div class="titlepage"><div><div><h5 class="title">
<a name="id445910"></a>Listing available providers</h5></div></div></div>
<p>
To list the available providers you must use the function <a class="link" href="libgda-gda-config.html#gda-config-get-provider-list" title="gda_config_get_provider_list ()"><span class="emphasis"><em>gda_config_get_provider_list ()
</em></span></a>
</p>
<p>
Here you see a function which lists available providers.
</p>
<div class="programlistingco">
<pre class="programlisting">
void
list_providers (void)
{
GList *prov_list;
GList *node;
GdaProviderInfo *info;
prov_list = gda_config_get_provider_list ();
for (node = g_list_first (prov_list); node != NULL;
node = g_list_next (node))
{
info = (GdaProviderInfo *) node->data;
g_print ("ID: %s\n", info->id);
}
gda_config_free_provider_list (prov_list);
}
</pre>
<div class="calloutlist"><table border="0" summary="Callout list">
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/1.png" alt="1" border="0"></p></td>
<td valign="top" align="left"><p>Our function.</p></td>
</tr>
<tr>
<td width="5%" valign="top" align="left"><p><img src="images/callouts/2.png" alt="2" border="0"></p></td>
<td valign="top" align="left"><p>Note that you must free the list when you finish using it.</p></td>
</tr>
</table></div>
</div>
</div>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="installation-provider"></a>Provider's specific information</h3></div></div></div>
<p>
This section provides information specific to each of the available
<span class="application">libgda</span> providers.
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="installation-provider-default"></a>Default provider</h4></div></div></div>
<p>
The <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> default provider is always installed
with <span class="application">libgda</span>, which means that you've got always a default
database system available for you. To connect to a default
provider's database, you only need to specify, in the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a> string,
a string of the form "URI=/path/to/the/database/file". When
you first connect to the new data source, the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> default
provider will create the database, in the path you specified
in the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a> string, if it does not exist. This default provider
uses XML as the format for that file.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="installation-provider-odbc"></a><a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> Provider</h4></div></div></div>
<p>
The <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> provider is a special case, since <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> is itself a
data access layer, the same as <span class="application">libgda</span>, So, in the case of the
<a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> provider, the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a> string is completely up to the
<a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> driver manager. That is, the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> provider does not
parse it all, nor does it try to understand what it means; it
simply passes it over to the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> library.
</p>
<p>
So, if you want to use <span class="application">libgda</span> with <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a>, you should first know
how to set up an <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> data source, and then just specify the
<a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a> string you would pass to the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> library in the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a>
string of the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> data sources.
</p>
<p>
There is a project called
<a class="ulink" href="http://www.unixodbc.org" target="_top">unixODBC</a>,
which provides some graphical tools to help you in
setting up <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=ODBC"><span class="acronym">ODBC</span></a> data sources. You may find it
interesting to give it a try.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="installation-provider-postgres"></a><span class="application">PostgreSQL</span> Provider</h4></div></div></div>
<p>
To use the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> <span class="application">PostgreSQL</span> provider, you'll need
the <span class="application">gda-postgres</span> package.
</p>
<p>
The <span class="application">PostgreSQL</span> provider accepts the following
arguments in the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> data source's <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a> string:
</p>
<div class="itemizedlist"><ul type="disc">
<li><p>
HOST: name of the host where
the database server is running. If it begins with a slash
then the protocol used is Unix-domain instead of TCP/IP and
its value is the name of the directory where the file is
stored. By default: /tmp.
</p></li>
<li><p>
HOSTADDR: IP of the host where the database server is
running (avoids DNS lookup). If this option has a value,
TCP/IP communications is used.
If neither a host name or host address is specified, the
connection will be established using a local Unix domain
socket.
</p></li>
<li><p>
PORT: Port number or socket filename extension for
Unix-domain connections.
</p></li>
<li><p>
DATABASE: name of the database you want to access. This one
is called 'dbname' in the <span class="application">PostgreSQL</span> documentation.
</p></li>
<li><p>
USER: user name to connect as.
</p></li>
<li><p>
PASSWORD: password if the connection requires it.
</p></li>
<li><p>
OPTIONS: trace/debug options to be sent to the server.
</p></li>
<li><p>
TTY: a file or tty for optional debug output from the
back-end.
</p></li>
<li><p>
REQUIRESSL: set to '1' to force SSL connection to the
back-end. Set to '0' to negotiate with server.
</p></li>
</ul></div>
<p>
The description of the parameters is almost copied from the
<span class="application">PostgreSQL</span> documentation. Refer to it for details on how some
environment variables can also set these parameters.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="installation-provider-mysql"></a><span class="application">MySQL</span> Provider</h4></div></div></div>
<p>
To configure a data source to access a <span class="application">MySQL</span> database,
you'll need to install the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> <span class="application">MySQL</span> provider (package
<code class="filename">gda-mysql</code>).
</p>
<p>
It accepts the following arguments in the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a>
string:
</p>
<div class="itemizedlist"><ul type="disc">
<li><p>
HOST: name of the host where the database server is running.
</p></li>
<li><p>
PORT: port number for connecting to the database server.
</p></li>
<li><p>
UNIX_SOCKET: socket file for connecting to the database server
(should not be defined with HOST and/or PORT).
</p></li>
<li><p>
DATABASE: name of the database you want to access.
</p></li>
<li><p>
USER: employ the specified user name for logging in to the
server.
</p></li>
<li><p>
PASSWORD: employ the specified password when connecting to the
database server.
</p></li>
<li><p>
USE_SSL: will use SSL (encrypted protocol) if specified and set to 1.
</p></li>
</ul></div>
<p>
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="installation-provider-sybase"></a><span class="application">Sybase</span> Provider</h4></div></div></div>
<p>
To use the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> <span class="application">Sybase</span> provider, you'll need
the <span class="application">gda-sybase</span> package.
</p>
<p>
The <span class="application">Sybase</span> provider accepts the following
arguments in the <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=GDA"><span class="acronym">GDA</span></a> data source's <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=DSN"><span class="acronym">DSN</span></a> string:
</p>
<div class="itemizedlist"><ul type="disc">
<li><p>
HOST: name of the host where the database server is
running.
</p></li>
<li><p>
USERNAME: user name to connect as.
</p></li>
<li><p>
APPNAME:
</p></li>
<li><p>
PASSWORD: password if the connection requires it.
</p></li>
<li><p>
DATABASE:
</p></li>
</ul></div>
<p>
</p>
</div>
</div>
<div class="footnotes">
<br><hr width="100" align="left">
<div class="footnote"><p><sup>[<a name="ftn.id445510" href="#id445510" class="para">1</a>] </sup>
It would be a good idea to add a command-line tool for managing
the configuration, as now, using <code class="systemitem">
GConf</code>, is not a matter of hacking on a config text
file, as it was before with <code class="function">gnome_config</code>.
The <a href="http://foldoc.doc.ic.ac.uk/foldoc/foldoc.cgi?query=API"><span class="acronym">API</span></a> for doing so is already available in the <code class="filename">
libgda-common</code>library, so it would be really easy.
Volunteers?
</p></div>
<div class="footnote"><p><sup>[<a name="ftn.id445780" href="#id445780" class="para">2</a>] </sup>It can be fixed, but it
is better not to run the risk of it.</p></div>
</div>
</div>
<div class="footer">
<hr>
Generated by GTK-Doc V1.10</div>
</body>
</html>
|
