firebird-docs — chat stuff about documentation

RE: [Firebird-docs] Re: Docs on the go

[Chris K. <ch...@e-...>]

Howdy,

> -----Original Message-----
> From: fir...@li...
>  On Behalf Of Lester Caine
> Sent: Thursday, 12 August 2004 2:05 PM
> To: fir...@li...
> Subject: Re: [Firebird-docs] Re: Docs on the go
> 
> Nigel Weeks wrote:
> 
> > If you received by attachments, please suggest subject areas to 
> > concentrate on, and I'll get working.
> 
> Like Firebird on FreeBSD :)
> 
> Building from Source

If you're talking about FreeBSD, then all you do is:

Update ports tree if necessary (FreeBSD Handbook covers this)
% cd /usr/ports/databases/firebird
% make install

The make install handles all the build tool dependencies for you.
If you want a binary package to install on other PCs, after make
install you do:

% make package

You then get a .tgz or .tbz (depending on FreeBSD version) package
that can be installed on other PCs by running:

pkg_add <name of package created above>

> First-time Configuration
> Users and Security - Protecting SYSDBA
> 
The make install on FreeBSD pops up a message detailing how to
change the sysdba password.

>  From your package could be dropped in the same place.
> Any expansion on FreeBSD would be nice. I will pick them off 
> and add them into the Using Firebird package. The Building 
> from source would be a good area, I still can't handle that ;)
> 
What, in general? Or just on FreeBSD?
From all the build pain that keeps popping up on firebird-devel from
time to time, I think the FreeBSD approach by taking care of the
build toolchain for you makes life simpler. It's just a pain for
me to keep maintaining it! :-)

> [snip]
> 
> --
> Lester Caine
> -----------------------------
> L.S.Caine Electronic Services

Regards,
Chris Knight
Systems Administrator
E-Easy
Tel: +61 3 6334 9995  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.e-easy.com.au 

Re: [Firebird-docs] Re: Docs on the go

[Nigel W. <nw...@ex...>]

If I do start filling up your TikiPro, will Paul V be able to use that info,
or will we have to write things twice?

If we had an online system that produced XML for Paul, HTML for people
searching the web, and PDF's to package up with releases...we'd be
cooking...

If someone's got an ssh account, I can put FireFly back into action - it'll
do this fairly well.

Nige.


----- Original Message ----- 
From: "Lester Caine" <le...@ls...>
To: <fir...@li...>
Sent: Thursday, August 12, 2004 2:05 PM
Subject: Re: [Firebird-docs] Re: Docs on the go


> Nigel Weeks wrote:
>
> > If you received by attachments, please suggest subject areas to
concentrate
> > on, and I'll get working.
>
> Like Firebird on FreeBSD :)
>
> Building from Source
> First-time Configuration
> Users and Security - Protecting SYSDBA
>
>  From your package could be dropped in the same place.
> Any expansion on FreeBSD would be nice. I will pick them off and add
> them into the Using Firebird package. The Building from source would be
> a good area, I still can't handle that ;)
>
> > If there was a web-based doc management system somewhere, that'd be
really
> > good for me!
>
> http://home.lsces.co.uk/TikiPro/
> is my attempt to get an online system working. I am being hampered at
> the moment because two sites that I had assumed my PHP system would just
> drop into and work but failed because Microshit have 'protected terminal
> server clients' so you don't know who they are - something that is
> fundamental to my system if I am to make an announcement calling a
> visitor to a particular client interview room.
>
> We also need to 'harvest' some of the other useful information that is
> floating around, but that will need clearing with the original author
> before we republish it. So the Borland stuff is out :)
>
> Expansion on the Reserved Word list sub pages would be most welcome.
>
> -- 
> Lester Caine
> -----------------------------
> L.S.Caine Electronic Services
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
>
>
> __________ NOD32 1.840 (20040811) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com
>
>

Re: [Firebird-docs] Re: Docs on the go

[Lester C. <le...@ls...>]

Nigel Weeks wrote:

> If you received by attachments, please suggest subject areas to concentrate
> on, and I'll get working.

Like Firebird on FreeBSD :)

Building from Source
First-time Configuration
Users and Security - Protecting SYSDBA

 From your package could be dropped in the same place.
Any expansion on FreeBSD would be nice. I will pick them off and add 
them into the Using Firebird package. The Building from source would be 
a good area, I still can't handle that ;)

> If there was a web-based doc management system somewhere, that'd be really
> good for me!

http://home.lsces.co.uk/TikiPro/
is my attempt to get an online system working. I am being hampered at 
the moment because two sites that I had assumed my PHP system would just 
drop into and work but failed because Microshit have 'protected terminal 
server clients' so you don't know who they are - something that is 
fundamental to my system if I am to make an announcement calling a 
visitor to a particular client interview room.

We also need to 'harvest' some of the other useful information that is 
floating around, but that will need clearing with the original author 
before we republish it. So the Borland stuff is out :)

Expansion on the Reserved Word list sub pages would be most welcome.

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

[Firebird-docs] Re: Docs on the go

[Nigel W. <nw...@ex...>]

As you know, I'm keen to see docs written for Firebird.
I started the Pocketbook series when I was at my previous employer, who had
hosting services, so I popper a P133 on the internet, and hosted the
document management system, 'FireFly' (Firebird based)

Unfortunately, my current employer has no hosting ability, so everything I
write has to be static, or hosted on someone elses infrastructure.

That said, I'm as keen as mustard to see docs written up.

If you received by attachments, please suggest subject areas to concentrate
on, and I'll get working.

If there was a web-based doc management system somewhere, that'd be really
good for me!

Nige.

>
>
> Greetings,
> Paul Vinkenoog
>
>
> __________ NOD32 1.840 (20040811) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com
>
>

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Phil S. <ph...@sh...>]

Nando Dessena wrote:

Hi,

> Boy do I hate ConTEXT! It must have something to do with the fact that
> in several cases it vaporized my files if I double-clicked on them and
> they were on a network path. 

FWIW, I have used ConTEXT for years, mainly to edit network based
files, and have never had any problems.

Phil

-- 
Firdbird has my support, has it got yours? -
www.firebirdsql.org/ff/foundation/
          Find a better way of life, play Marbles - www.marillion.com
  ICQ: 760757 | AIM: pjshrimpton | Y!: pjshrimpton |
pjs...@ja...

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Paul V. <pa...@vi...>]

Nando wrote:

> Boy do I hate ConTEXT! It must have something to do with the fact
> that in several cases it vaporized my files if I double-clicked on
> them and they were on a network path.

Milan wrote:

> I'm also an ex-ConText user. It made my Windows crash too many
> times. I started to use SciTE after that, and I find it perfect.

Thanks for the warnings, guys! I'll look into this and possibly dump
Context too... although I love it and have never experienced such
problems. But then I rarely access text files over my network.


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Milan B. <mi...@km...>]

Nando Dessena wrote:
> P> Notepad doesn't, but
> P> I don't care because I use Context as my default text (and XML)
> P> viewer/editor. During installation you even have the option of
> P> replacing Notepad with Context (for apps that hard-link to
> P> Notepad.exe). I did this, and my life is much happier now :-)
> 
> Boy do I hate ConTEXT! It must have something to do with the fact that
> in several cases it vaporized my files if I double-clicked on them and
> they were on a network path. Not a pleasant experience. I never got
> around to discover whether it was ConTEXT or some other actor in my
> environment, I just deleted it together with its ugly option of
> overwriting notepad and forgot it. Now the name is enough to make me
> shiver. ;-)

I'm also an ex-ConText user. It made my Windows crash too many times. I 
started to use SciTE after that, and I find it perfect.

Milan.

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Nando D. <na...@de...>]

Paul,

P> Notepad doesn't, but
P> I don't care because I use Context as my default text (and XML)
P> viewer/editor. During installation you even have the option of
P> replacing Notepad with Context (for apps that hard-link to
P> Notepad.exe). I did this, and my life is much happier now :-)

Boy do I hate ConTEXT! It must have something to do with the fact that
in several cases it vaporized my files if I double-clicked on them and
they were on a network path. Not a pleasant experience. I never got
around to discover whether it was ConTEXT or some other actor in my
environment, I just deleted it together with its ugly option of
overwriting notepad and forgot it. Now the name is enough to make me
shiver. ;-)

I am a happy user of NoteTab lite at work - I only have notepad on my
notebook but I'll fix it soon. ;-)

P.S. I'm not the only one. See http://tinyurl.com/6vq72

Ciao
-- 
Nando Dessena
mailto:na...@de...

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Paul V. <pa...@vi...>]

Hi Nando,

> P> Somewhere after a version upgrade (I don't remember which one)
> P> XXE suddenly wrote out prettified, very readable XML files.

> Yep. The only problem is that it is using LF as a line separator
> instead of CRLF, but this is a problem only under Windows and an
> easily solved one anyway.

Word and Wordpad display LF-files correctly. Notepad doesn't, but
I don't care because I use Context as my default text (and XML)
viewer/editor. During installation you even have the option of
replacing Notepad with Context (for apps that hard-link to
Notepad.exe). I did this, and my life is much happier now :-)


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Nando D. <na...@de...>]

Paul,

P> If you press the button with the paragraph sign (near the right end of
P> the toolbar) you can choose between <section> and <sectN> tags. The
P> ones that aren't allowed at the cursor position will be disabled.

Well, that was my problem. I couldn't figure out why I had the sect*
options always disabled. I think I have got the rationale now.

P> To create a sibling section following the one you're in, it can be
P> done even quicker: in the Node Path bar (below the toolbar, this can
P> show e.g. "book chapter section section para" or "article sect1 sect2
P> para warning", depending on where you are), Ctrl-Click on the node you
P> want to "duplicate" and a new, empty node of that type will be added.
P> With Shift-Click, the new node will be inserted before the current
P> one. This works for all types of nodes, not only sections.

Precious tip!

P> Somewhere after a version upgrade (I don't remember which one) XXE
P> suddenly wrote out prettified, very readable XML files. Via Options ->
P> Save you can configure indentation, line length etcetera. It pays to
P> check for new versions every now and then; they seem to be getting a
P> lot of user feedback, and listening to it.

Yep. The only problem is that it is using LF as a line separator
instead of CRLF, but this is a problem only under Windows and an
easily solved one anyway.

Thanks a lot!
-- 
Nando Dessena
mailto:na...@de...

Re: [Firebird-docs] XXE, sect* tags and prettifying source files

[Paul V. <pa...@vi...>]

Hi Nando,

> it looks to me that XXE does not allow <sect*> tags in an easy
> way. Is that true?

If you press the button with the paragraph sign (near the right end of
the toolbar) you can choose between <section> and <sectN> tags. The
ones that aren't allowed at the cursor position will be disabled.

To create a sibling section following the one you're in, it can be
done even quicker: in the Node Path bar (below the toolbar, this can
show e.g. "book chapter section section para" or "article sect1 sect2
para warning", depending on where you are), Ctrl-Click on the node you
want to "duplicate" and a new, empty node of that type will be added.
With Shift-Click, the new node will be inserted before the current
one. This works for all types of nodes, not only sections.

(There are also other ways, e.g. via the menus or the "Insert After"
box, but these take more time.)

> I have only found the ability to use <section> tags, optionally
> nested, but IIRC it's not the recommended practice, is it?

It wasn't, but our transformation stylesheets have been improved at
this point so now it doesn't matter anymore. Use what you like.

> Also, it produces unreadable XML code. Can it be instructed to
> prettify it some way or should I open the files with XML Spy to
> achieve that?

Somewhere after a version upgrade (I don't remember which one) XXE
suddenly wrote out prettified, very readable XML files. Via Options ->
Save you can configure indentation, line length etcetera. It pays to
check for new versions every now and then; they seem to be getting a
lot of user feedback, and listening to it.


Greetings,
Paul Vinkenoog

[Firebird-docs] XXE, sect* tags and prettifying source files

[Nando D. <na...@de...>]

Hello,
it looks to me that XXE does not allow <sect*> tags in an easy way. Is that
true? I have only found the ability to use <section> tags, optionally
nested, but IIRC it's not the recommended practice, is it?

Also, it produces unreadable XML code. Can it be instructed to
prettify it some way or should I open the files with XML Spy to
achieve that?

Thanks
-- 
Nando Dessena
mailto:na...@de...

Re: [Firebird-docs] Where to place FlameRobin documentation

[Nando D. <na...@de...>]

Paul,

>> Don't worry - when FR is production ready you'll know it. ;-)

P> In quadraphony, right? :-)

No doubt. :-)
-- 
Nando Dessena
mailto:na...@de...

Re: [Firebird-docs] Where to place FlameRobin documentation

[Paul V. <pa...@vi...>]

Hi Nando,

> I wanted to keep developer docs and user docs separated. As it looks
> like we won't be using DocBook but wiki for developer docs, I agree
> that a <book> is better suited.

Or even if you will use DocBook for the devdocs, you could make two
<book>s - within a <set> or not. In either case the user docs book
would later be easy to integrate.


> Don't worry - when FR is production ready you'll know it. ;-)

In quadraphony, right? :-)


Ciao,
Paul

Re: [Firebird-docs] Where to place FlameRobin documentation

[Nando D. <na...@de...>]

Paul,

P> That said, if you like our doc build system, why not copy it to the FR
P> project (that's what it's Open Source for) and use it for your docs
P> (the DocBook sources of which would be committed to FR's CVS tree) ?

that's a lot of stuff; I'm a bit concerned about duplicating
everything (and keeping it in sync). OTOH if someone else needs to
contribute documentation to FR (unlikely, for now) (s)he should be
able to checkout everything needed from the FlameRobin CVS tree...

P> Your top level node should IMO be a <book>: FR documentation covers
P> "only" one tool, so no need for a <set> like with the Firebird docs.

I wanted to keep developer docs and user docs separated. As it looks
like we won't be using DocBook but wiki for developer docs, I agree
that a <book> is better suited.

P> By the way, if you alert us as soon as you guys feel that FR is mature
P> and robust enough for the average Firebird user, we can at least
P> include a link in the Quick Start Guide (along with links to other
P> usable frontends).

Don't worry - when FR is production ready you'll know it. ;-)

Ciao
-- 
Nando Dessena
mailto:na...@de...

Re: [Firebird-docs] Where to place FlameRobin documentation

[Paul V. <pa...@vi...>]

Hi Nando,

> I succeeded in writing a first piece of documentation for FlameRobin
> (fka fbmanager) in DocBook and integrate it into the firebirddocs
> build just to see the output (which looks nice enough - I just need
> to add some more DocBook tags).

> Once Paul suggested that I put the FR documentation up as a separate
> book, so I have added a <book> section to firebirddocs.xml; is that
> OK? alternatively, I could make it a different set altogether.

> The problem is that I cannot say whether FR will ever actually be
> part of the Firebird project or keep on as a satellite independent
> project.  In the latter case I'm not even sure I should use the
> Firebird-docs build system, although I find it very useful
> regardless.

The discussion about which GUI (if any) to pack with Firebird
distributions is stil raging. Also, like you write above, it's unsure
if FR will be merged with the Firebird project later. So at least for
now we can't include the FR docs in the Firebird docset, as this would
suggest that FR is our officially endorsed GUI.

That said, if you like our doc build system, why not copy it to the FR
project (that's what it's Open Source for) and use it for your docs
(the DocBook sources of which would be committed to FR's CVS tree) ?

Your top level node should IMO be a <book>: FR documentation covers
"only" one tool, so no need for a <set> like with the Firebird docs.

If you do it like this, you can happily manage your docs as long as
FR is an independent project; and if it should ever be merged with
Firebird, the docs would be easy to integrate. Even if the projects
wouldn't merge entirely but FR would become Firebird's officially
recommended tool we could integrate the docs.

For would-be FlameRobin doccers instructions you could link to
  http://www.firebirdsql.org/manual/docwritehowto.html
  (PDF version at:
   http://www.firebirdsql.org/pdfmanual/Firebird-Docwriters-Info.pdf)
or steal the sources and adapt them for FR. Or write your own. Or do
both.


By the way, if you alert us as soon as you guys feel that FR is mature
and robust enough for the average Firebird user, we can at least
include a link in the Quick Start Guide (along with links to other
usable frontends).


Greetings,
Paul Vinkenoog

[Firebird-docs] Where to place FlameRobin documentation

[Nando D. <na...@de...>]

Hello,
picking up from where I left quite some time ago...

I succeeded in writing a first piece of documentation for FlameRobin
(fka fbmanager) in DocBook and integrate it into the firebirddocs
build just to see the output (which looks nice enough - I just need to
add some more DocBook tags).

Once Paul suggested that I put the FR documentation up as a separate
book, so I have added a <book> section to firebirddocs.xml; is that
OK? alternatively, I could make it a different set altogether.

The problem is that I cannot say whether FR will ever actually be part
of the Firebird project or keep on as a satellite independent project.
In the latter case I'm not even sure I should use the Firebird-docs build
system, although I find it very useful regardless.

Thoughts?
-- 
Nando Dessena
mailto:na...@de...

Re: [Firebird-docs] this doc subject vs. ibphoenix developers

[Paul V. <pa...@vi...>]

Hi h zhang,

> I am far from being a database expert.  But I think InterBase is
> better than MySQL generally speaking.

And Firebird, in turn, is better than InterBase :-)


Greetings,
Paul Vinkenoog

Re: [Firebird-docs] this doc subject vs. ibphoenix developers

[Lester C. <le...@ls...>]

h zhang wrote:

> I am far from being a database expert.  But I think InterBase is better than
> MySQL generally speaking.  But MySQL has large user pool and MySQL has
> documents, desktop tool such as mysqlcc for free.  If FireBird documents
> will charge hundreds dollars forever, then it may not catch up with MySQL in
> the open source database community.

You can pay for MySQL documentation as well as needing to pay licence 
fees for some uses and versions of MySQL. The chargeable Firebird 
documents are not essential just as the chargeable MySQL aren't. But at 
least with Firebird you don't have to worry if you are going to hit a 
licence fee some time.

The free Firebird stuff is more capable than a lot of the Free MySQL 
stuff anyway ;)

-- 
Lester Caine
-----------------------------
L.S.Caine Electronic Services

Re: [Firebird-docs] this doc subject vs. ibphoenix developers

[h z. <hui...@ho...>]

Thanks!  Now  I got the whole picture.  I was wondering why someone is
working on the documents and the IBPhoenix already have them done.  And the
documents, unlike the software (source code closed), will be hard to tell if
it is original written by this project or copy from IBPhoenix.

I am far from being a database expert.  But I think InterBase is better than
MySQL generally speaking.  But MySQL has large user pool and MySQL has
documents, desktop tool such as mysqlcc for free.  If FireBird documents
will charge hundreds dollars forever, then it may not catch up with MySQL in
the open source database community.


"Helen Borrie" <he...@tp...> wrote in message
news:5.2...@ma......
> At 04:20 PM 3/08/2004 -0700, you wrote:
> >Hi, unlike the MySQL.  FireBird doesn't have the free detailed documents.
> >Is this subject planning to make the documents for free but as good as
> >ibphoenix developers CD which cost hundreds bucks?
>
> In time, yes.  The IBPhoenix policy is to charge for the commissioned
> documents until they have paid for themselves and then to open-doc them to
> the project.
>
> The Quick Start Guide (which actually has always been free) has already
> passed into this project.  Next to come will be the Using Firebird book
> from the CD which, though it hasn't paid for itself yet, is now superseded
> by the recently-published paper book, "The Firebird Book".
>
>
> >If that is so, I may wait for the free ones from this sub-project.
>
> You may. :)  Actually, there's a lot going on around the project in the
> area of documentation.  Since the Firebird website is about to undergo a
> makeover (over the next 3 months) you might find it easier in future to
> locate documentation you need.
>
>
> >I am going to migrate my old InterBase 6.0 open source version Server to
> >FirdBird1.5.  I will only use it for simple database management to
support
> >web sites etc.  I assume if I stay with my "old" developer's way which th
e
> >Interbase 6.0 documents taught me, I can still manage to run the FireBird
> >1.5 with Interbase 6.0 documents.
>
> Well, no Firebird documentation is going to try to change your ways with
> regard to developing applications.  A better database engine doesn't
> magically create better programmers or designers. If you wrote good apps
> for IB 6, you'll write good apps for Firebird.
>
> Currently, you can't get everything you need FREE in a single document,
but
> the IB6 beta docs + 1.0 Release notes + 1.5 Release notes are all free,
and
> together cover everything you need to know about Firebird, for those who
> want to take the trouble to download them and READ them.
>
> Writing documentation takes a lot of effort, testing and people
> hours.  It's a job that is never finished.  It wouldn't hurt you to be a
> slightly grateful that there are people working long hours--for love, not
> money--or contributing their own money, so that people like you can get
> easy access to FREE documentation to accompany your FREE software...
>
> Helen
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> Firebird-docs mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-docs
>

Re: [Firebird-docs] CREATE USER in FB 1.51?

[Christian M. <cr...@gm...>]

Hi!

Milan Babuskov wrote:

>> Is it possible to create a user in FB using SQL statements?
> Yes, but you need to use some UDF library that does it, like rFunc.
> Please ask further questions at firebird-support group at groups.yahoo.com.

Thanks for your two's help, I´ve already signed up for that group. I 
thought this question could belong here.

regards,
    Chriss

Re: [Firebird-docs] this doc subject vs. ibphoenix developers CD

[Helen B. <he...@tp...>]

At 04:20 PM 3/08/2004 -0700, you wrote:
>Hi, unlike the MySQL.  FireBird doesn't have the free detailed documents.
>Is this subject planning to make the documents for free but as good as
>ibphoenix developers CD which cost hundreds bucks?

In time, yes.  The IBPhoenix policy is to charge for the commissioned 
documents until they have paid for themselves and then to open-doc them to 
the project.

The Quick Start Guide (which actually has always been free) has already 
passed into this project.  Next to come will be the Using Firebird book 
from the CD which, though it hasn't paid for itself yet, is now superseded 
by the recently-published paper book, "The Firebird Book".


>If that is so, I may wait for the free ones from this sub-project.

You may. :)  Actually, there's a lot going on around the project in the 
area of documentation.  Since the Firebird website is about to undergo a 
makeover (over the next 3 months) you might find it easier in future to 
locate documentation you need.


>I am going to migrate my old InterBase 6.0 open source version Server to
>FirdBird1.5.  I will only use it for simple database management to support
>web sites etc.  I assume if I stay with my "old" developer's way which the
>Interbase 6.0 documents taught me, I can still manage to run the FireBird
>1.5 with Interbase 6.0 documents.

Well, no Firebird documentation is going to try to change your ways with 
regard to developing applications.  A better database engine doesn't 
magically create better programmers or designers. If you wrote good apps 
for IB 6, you'll write good apps for Firebird.

Currently, you can't get everything you need FREE in a single document, but 
the IB6 beta docs + 1.0 Release notes + 1.5 Release notes are all free, and 
together cover everything you need to know about Firebird, for those who 
want to take the trouble to download them and READ them.

Writing documentation takes a lot of effort, testing and people 
hours.  It's a job that is never finished.  It wouldn't hurt you to be a 
slightly grateful that there are people working long hours--for love, not 
money--or contributing their own money, so that people like you can get 
easy access to FREE documentation to accompany your FREE software...

Helen

[Firebird-docs] this doc subject vs. ibphoenix developers CD

[h z. <hui...@ho...>]

Hi, unlike the MySQL.  FireBird doesn't have the free detailed documents.
Is this subject planning to make the documents for free but as good as
ibphoenix developers CD which cost hundreds bucks?

If that is so, I may wait for the free ones from this sub-project.

I am going to migrate my old InterBase 6.0 open source version Server to
FirdBird1.5.  I will only use it for simple database management to support
web sites etc.  I assume if I stay with my "old" developer's way which the
Interbase 6.0 documents taught me, I can still manage to run the FireBird
1.5 with Interbase 6.0 documents.

Am I right?

Thanks!

Re: [Firebird-docs] multiuser possibilities with embedded server

[Paul V. <pa...@vi...>]

Hi John,

Please use fir...@ya... for support questions.
This list here is for talk about the development of Firebird docs.

Greetings,
Paul Vinkenoog


> someone experience with this?
>
> You may run any number of applications with the embedded server
> without any conflicts. Having IB/FB server running is not a problem
> either. But you should be aware that you cannot access single
> database from a number of the embedded servers simultaneously,
> because they have SuperServer architecture and hence exclusively
> lock attached databases.

[Firebird-docs] multiuser possibilities with embedded server

[John v. T. <joh...@st...>]

Hey,

someone experience with this?

You may run any number of applications with the embedded server without any
conflicts. Having IB/FB server running is not a problem either. But you
should be aware that you cannot access single     database from a number of
the embedded servers     simultaneously, because they have SuperServer
architecture     and hence exclusively lock attached databases.

greetz,

John