Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Leyne, Sean
Dmitry, > > fb_backup, fb_security, fb_fixup, fb_stats and fb_precompile > > I believe gpre stands for preprocess, not precompile. Ok, "fb_preprocess" it is! ;-) > > I realize that the names are longer than the original, but they are > > much more meaningful > > Speaking about meanings, I'd

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Dimitry Sibiryakov
18.11.2012 18:31, Leyne, Sean wrote: > I am not sure that nbackup is the ideal backup that it could be. But this is exactly what in other SQL servers (Oracle at least) is called "backup". -- WBR, SD. -- Monitor y

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Leyne, Sean
> > Speaking about meanings, I'd suggest this change: > > > > gbak -> fb_dump > > nbackup -> fb_backup > > > > because IMO it better reflects their goals. > > Although I was the one who approached Nikolay about the ideas for > nbackup, and paid for the development, I am not sure that nbackup is

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Pierre Y.
What about something like git/hg/svn and al. ? Executable names are : git-clone, git-status... but are wrapped by a single "git" loader that forwards to the right executable based on the first argument. If the executable "fb" is already taken, maybe "fbt" (Firebird Tools) is not so, or, more long

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Kjell Rilbe
Den 2012-11-18 19:04 skrev Leyne, Sean såhär: >>> Speaking about meanings, I'd suggest this change: >>> >>> gbak -> fb_dump >>> nbackup -> fb_backup >>> >>> because IMO it better reflects their goals. >> Although I was the one who approached Nikolay about the ideas for >> nbackup, and paid for the

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Leyne, Sean
> > I was simply trying to say, that I even with my history with the utility, I > have a nagging feeling that nbackup could be better. So, I am not sure if > nbackup is worthy of the official blessing that "fb_backup" conveys. > > I know that I had problems with Nbackup when I tried it with our

[Firebird-devel] [FB-Tracker] Created: (CORE-3987) CHECK CONSTRAINT with sub-select fails to raise exception when it should

2012-11-18 Thread Jason Wharton (JIRA)
CHECK CONSTRAINT with sub-select fails to raise exception when it should Key: CORE-3987 URL: http://tracker.firebirdsql.org/browse/CORE-3987 Project: Firebird Core Issu

Re: [Firebird-devel] /src/msg/msg.gdl in trunk?

2012-11-18 Thread Alex Peshkoff
On 11/17/12 13:56, Mark Rotteveel wrote: > I was looking at the definition of the msg database used in the build. > As far as I can tell msg.gdl has been replaced with msg.sql. Is there a > reason it hasn't been deleted? > Suppose no good reason. Specially taking into an account we do not support

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Dmitry Yemanov
17.11.2012 13:54, Philippe Makowski wrote: > > I guess it depends on the keyboard layout, too. > yes, and we have fb_lock_print, fb_inet_server, fbsvcmgr, fbtracemgr, > fb_config, fbguard Just a note. There's no fb_inet_server or fb_smp_server anymore. I don't know anything about fb_config, is it

Re: [Firebird-devel] Firebird 3, time to rename conflict names ?

2012-11-18 Thread Alex Peshkoff
On 11/19/12 11:04, Dmitry Yemanov wrote: > 17.11.2012 13:54, Philippe Makowski wrote: >> I guess it depends on the keyboard layout, too. >> yes, and we have fb_lock_print, fb_inet_server, fbsvcmgr, fbtracemgr, >> fb_config, fbguard > Just a note. There's no fb_inet_server or fb_smp_server anymore.