firebirdWebAdmin bugs tracker

The starting point here is just what base I should be using, and what version number should be used. This is not unusual and for example I have a fork of bitweaver that has an 'lsces' extension to the verison number. I've adopted a base version of '5' for both since they are both targeting Firebird 5 and will be tidied to match PHP8.5 in the near future. The main target should be to make my own code available for others to use should they wish to and while in the past I've prefered to use Mercurial for code version control, it is obvious today that git has to be the base today even given my own dislikes of how it is managed on github? While I have not checked fully, I think everything I am using today is managed on github and In index of that needs to be created. My own Project Index covers code I was working on 20+ years ago and much of that is now obsolite, so a major update of that has to be higher on the todo list.

So what do I still need to address on firebirdWebAdmin before making the demo available again.

1/ Accessories -> User Defined Functions Is showing internal functions rather than just the user defined ones. This I think is an FB5 change and I need to establish just what functions are being displayed. The system table details has changed as well which has sort of been corrected so that the variables are now listed.

2/ Data -> Export Data Gives an error currently, fun with legacy functions being able to access different parameters and work slightly differently. In this case the link to the database handle is missing and previously PHP would just have used the right version of the function. Now we need to create different functions, but some of this is IN the firebird driver!

3/ Admin -> Server Statistics ... 'Unable to access lock table.' Yet using the exec call to 'fb_lock_print' in a command prompt works fine. Not sure what to try next.

4/ Admin -> Backup ... Nothing happening when using this

4/ While it can be nice that the folded pages remember their last display, it can also be irritating and so I am thinking that I need a clear function to allow starting a new view of things.

5/ FB5 data types have been added, and while some uses have been checked, I need a fuller test suite to ensure all uses work correctly. Using 128bit variables need to be handled when required in PHP using bcmath extension, much like using mbstring for UTF8 strings is needed to properly handle UTF8 data from the database even if the legacy string code manages well most of the time. (Need to address this in the ibtest program as well)

I need to touch base with someone who understands all the new stuff that I have not been following myself ...