Recent changes to feature-requests

restore from "local" file

Andre Meyer — Tue, 16 Nov 2004 20:47:23 -0000

it would be great if it were possible to restore from
browser-uploaded file. maybe as if you would attach a
file here.

./firebird/aliases.conf

Phil Palan — Thu, 11 Mar 2004 21:51:42 -0000

Is there a drawback to using aliases?
(ie. comment out lines 45-47 in database.php so that one
can enter an alias into the database login form.)
Thanks
Phil

Documentation: exec(): Unable to fork

Dale Mullins — Thu, 04 Mar 2004 13:12:12 -0000

Running Windows 2003 Server + PHP 4.3.4, I would get
this error whenever an external command was executed
(isql, fb_lock_print, etc):

exec(): Unable to fork

After searching Google Groups, the fix I used was to give
the web server user on Windows
(IUSR_<computername>) read & execute permissions on
cmd.exe (located in %system32% folder).

Obviously, this could be a security issues in your
situation, so use at your own risk.

You may want to include this information in the README,
configuration.inc, and/or the beginners guide by Lester
Caine @ http://www.ibphoenix.com/main.nfs?
a=ibphoenix&page=ibp_beginners_php

hostname entry needed for restore subsection

Andrej Surkov — Wed, 17 Dec 2003 09:47:48 -0000

'Restore target' subsection of 'Restore' subsection of
Admin page definitely needs to have hostname input
window, because, generaly, we want to restore database
to remote machine.

additional config examples fb/ib and local/remote

Jeff Stern — Tue, 09 Dec 2003 23:19:27 -0000

hi,

i did see a couple of examples for how to set up the
configuration.inc.php but i would like to see some
additional information either added to the file itself
(before each of the parameters) or to the README.

it would be nice to see ***FOUR** examples: 2 for
firebird, 2 for interbase -- and local AND remote
database examples for each.

for instance, questions i had i did not see answered
anywhere, which seemed to relate more to REMOTE setup
for IB:

1) for dealing with remote databases: does DEFAULT_PATH
refer to the default path on the database server? or
for the client interbase stuff on the web server? for
instance, if on the db server, my database is
"/databases/special/thisone.gdb" and on the web server,
the interbase stuff is in "/opt/interbase" does
DEFAULT_PATH refer to "/databases/special/" or to
"/opt/interbase/"?

2) whether final "/"'s are needed in variables which
refer to paths/directories -- this would be nice to see
answered

3) in the following setup line:

define('SECURITY_DB',
'/usr/local/firebird/security.fdb'); // where to look
for the interbase security database.

what does this mean for a remote interbase setup? what
do i set this to? i could not find an isc4.gdb anywhere
on my web server (the machine with the client IB
bins).. i assume it's on the db server somewhere, and i
could ask my db admin -- but what do i set this value
to in this case?

4) same thing for this line:

define('BACKUP_DIR', '/opt/interbase/backup/'); //
define this to restrict the location for backup files

my IB server is remote. do i make a
/opt/interbase/backup directory HERE (on the web
server)? or do i refer to a special place on the DB
server (and thus have to ask my DB admin)? or do i put
NOTHING?

etc etc etc

once i do get an interbase ibwebadmin setup going well,
i can submit an IB/REMOTE example..

thanks,
jeff stern

Firebird utilities name change

Dale Mullins — Wed, 28 May 2003 00:07:15 -0000

Using Firebird 1.5 RC2 (Windows platform):

"iblockpr.exe" is now "fb_lock_print.exe". Not sure about
Linux version, but I assume the ".exe" is dropped but
names are still changed.

The causes the server statistics to fail:
admin.php, line 182

I'd like to request a new "define" in configuration.inc.php.
Maybe something like:

define('LOCK_PRINT', 'iblockpr');

which could be changed to work with Firebird and used
within admin.php

Or any other solution you may like that will fix this
problem.

I am sure other issues with the forking will follow, but
hopefully you will continue to help support Firebird. :)

Thanks,
Dale

Change isql binary verification method

Dale Mullins — Wed, 30 Oct 2002 08:16:03 -0000

In the file "script_start.inc.php"

This section of code:

if ($s_binpath != BINPATH) {
if (!is_dir(BINPATH)
|| !is_file(BINPATH.'isql')) {

will cause a *warning* to be displayed on Windows
platform since the filename is actually isql.exe, not isql .

Fix 1. An "OR" operator could be added to the code
above and also check for BINPATH.'isql.exe'

or, probably a better solution :)

Fix 2. Define a new variable in configuration.inc.php and
use it in place of 'isql'

define('ISQLBIN', 'isql'); //unix
define('ISQLBIN', 'isql.exe'); //windows

Implement aliases/profiles

Dale Mullins — Wed, 30 Oct 2002 07:59:32 -0000

A nice feature would be the ability to store
aliases/profiles for quick selection when connecting to a
database in ibWebAdmin.

For example, have a configuration file that contains the
values needed to log into a database (the values entered
in the "Login to database" panel). This alias/profile can
be recalled quickly with a drop-down listbox on the
same panel.

Ability to save database name, host, username,
password?, role, cache, character set, and dialect and
populate these values for the connection by selecting an
alias from the listbox.

This does not necessarily need to be end-user
created/modified. Just a configuration file on the web
server that can be maintained by the web/db
administrator.

Allow multiple database extensions

Dale Mullins — Wed, 30 Oct 2002 07:38:05 -0000

ibWebAdmin allows you to restrict the database
extension that is allowed to be used (by default, this
is .gdb).

At this time there can only be one. You may also set it
to nothing and there is no restrictions in place, which
may be a security issue to some users of ibWebAdmin.

Since the database extension can be specified by the
creator, it is becoming common practice for Firebird
users to use a different extension (like .fdb) and the next
version of Interbase will default to .ib .

The ability to specify multiple extensions in the
configuration file would be a useful feature.