Bug showing details/editing record?

I

Ignorant Fool

Guest
I'm getting more and more impressed with dadabik, easy to setup and use, even for non-technical people like myself!

However, I may have come across a bug, I don't know:

I've setup a terminology database with just 1 table and something like 10 fields. The database is pretty huge, it contains around 120,000 records. For some records in the database I can't display the details of a found record and when I try to edit such a record, the Edit screens comes up but all fields are empty.

The records which have this behaviour have nothing much in common, they don't share any funny special characters or anything like that. The only thing they have in common is that they're in a contiguous range. I don't have any problem with the records before and after that range. Also, I don't have any problem with those records in phpMyAdmin.

Is there anything I can do to fix this or to find out what's going on?
 
E

Eugenio

Guest
Ignorant Fool wrote:
>
> I'm getting more and more impressed with dadabik, easy to
> setup and use, even for non-technical people like myself!
>
> However, I may have come across a bug, I don't know:
>
> I've setup a terminology database with just 1 table and
> something like 10 fields. The database is pretty huge, it
> contains around 120,000 records. For some records in the
> database I can't display the details of a found record and
> when I try to edit such a record, the Edit screens comes up
> but all fields are empty.
>
> The records which have this behaviour have nothing much in
> common, they don't share any funny special characters or
> anything like that. The only thing they have in common is
> that they're in a contiguous range. I don't have any problem
> with the records before and after that range. Also, I don't
> have any problem with those records in phpMyAdmin.

Can you can send me the dump of your db and specify the records that cause the problem?
I can in this way see the problem.

Eugenio.

(Latest version of DaDaBIK when this message was posted: 2.2.1)
 
Top