Bugs in Dadabik v1.5b

[Ap Muthu]

If a Date field is empty, then an error is caused on execution of a search form even without entering the date field values.

Also in the search form - the display of the operator =<> is one row higher than the 3 part date selection field with no indication of day, month and year labels. A nice calendar month based date chooser would be nice!

If we refresh the internal table, the labels for the fields are lost - the records in the internal table pertaining to the fields that have not changed need not be touched for field values like labels, size, presence/absence in search and insert forms. This can be done by enabling partial or full resetting of the internal table - options - in the admin.php.

Also a means to use this pattern of internal table to make a multi table editor interface and an elucidation of User_ID usage would be useful.

 

[Eugenio]

Ap Muthu wrote:

> If a Date field is empty, then an error is caused on
> execution of a search form even without entering the date
> field values.

I'm not able to reproduce that bug, can you send me a dump of your main table (just a piece) and of your internal table?

> Also in the search form - the display of the operator =<> is
> one row higher than the 3 part date selection field with no
> indication of day, month and year labels. A nice calendar
> month based date chooser would be nice!

I know, it's a problem of HTML layout, it depends on the fact that I use the same table for search, insert and update.

> If we refresh the internal table, the labels for the fields
> are lost - the records in the internal table pertaining to
> the fields that have not changed need not be touched for
> field values like labels, size, presence/absence in search
> and insert forms. This can be done by enabling partial or
> full resetting of the internal table - options - in the
> admin.php.

As I wrote in the documentation, the updating of the internal table is a feature that I haven't tested enough, in the next releases of DaDaBIK that feature will be fixed and a new graphic manager for the internal table will be included.

> Also a means to use this pattern of internal table to make a
> multi table editor interface

I know, this is a feature request, maybe in the next releases of DaDaBIK.

> and an elucidation of User_ID
> usage would be useful.

A user_ID field is a field in which, automatically (you don't need to include the field in the insert form), when a new record is inserted, DaDaBIK insert the username of the current user. It's useful in an intranet/password-protected site.


(Latest version of DaDaBIK when this message was posted: 1.5b)

 

[Eugenio]

Ap Muthu wrote:

> If we refresh the internal table, the labels for the fields
> are lost - the records in the internal table pertaining to
> the fields that have not changed need not be touched for
> field values like labels, size, presence/absence in search
> and insert forms. This can be done by enabling partial or
> full resetting of the internal table - options - in the
> admin.php.

I'm re-testing the update table feature (the current one, v1.5b) and, actually, it works fine: when you add new fields in your main table you have just to re-call admin.php and click the "install/update internal table" button. All the old fields propreties won't be changed.

When you rename a field, instead, you have to rename manually the name_field properties of the internal table. When you delete a field, you have to delete the corrisponding record from the internal table.

The correct steps are:
- rename name_field if you have changed some field names, then
- delete the corrsiponding records if you have delete some fields, then
- execute "install/update internal table" if you have add some fields.


(Latest version of DaDaBIK when this message was posted: 1.5b)

 

[Eugenio]

Eugenio wrote:

> I'm re-testing the update table feature (the current one,
> v1.5b) and, actually, it works fine: when you add new fields
> in your main table you have just to re-call admin.php and
> click the "install/update internal table" button. All the old
> fields propreties won't be changed.

I just want to underline that, to use the update internal table feature, you need to have the fields in the same order both in the main table and in the internal one i.e. you have to refresh the internal table always using DaDaBIK, and not by inserting a new row at the end of the internal table when you add new fields in the main one.

I've also just discovered a bug in that feature, if you have special characters in the internal table (such as '), the feature won't work, I've missed some addslashes() functions in manage_internal_db.php.

The bug is now fixed and the next release of DaDaBIK will contain the bugfix, togheter with a nice administration interface for the internal table.

(Latest version of DaDaBIK when this message was posted: 1.5b)