Database Settings -> confunsing information and possibility of setting wrong values
Original Reporter info from Mantis: valdir.marcos @valdir.marcos
-
Reporter name: Valdir Marcos
Original Reporter info from Mantis: valdir.marcos @valdir.marcos
- Reporter name: Valdir Marcos
Description:
- Attached image shows that I can see and select wrong SQLTransaction components that are neither on form itself nor in its Uses list. Same behavior for properties such as Database, Transaction, DataSource, etc.
Coming from Delphi, I think that the possibility of setting wrong information is a problem, but I was told this is by Lazarus design:
"Error - Transaction of connection not set"
http://forum.lazarus.freepascal.org/index.php/topic,42410.msg296241.html#msg296241
- Pollution caused by wrong information and its consequences.
Thinking about a project with hundreds of forms and data modules, showing wrong information that is not related to that SQLQuery component turns out to be a type of pollution that lowers productivity and assertiveness and increases the chance of errors. As it's happening now, some of those errors are very difficult to solve because one does not know their origin or how to build a sample project to reproduce the problem.
Steps to reproduce:
Create a project with many datamodules and forms with many TIBConnection, TSQLTransaction, TSQLQuery and TDatasource.
Having many data modules and forms opened simultaneously shows the problem.
I have attached a small project that shows the problem. As the project grows to hundreds of data modules and forms, the problem becomes a real nightmare.
Mantis conversion info:
- Mantis ID: 34686
- OS: Windows
- OS Build: 7 and 10
- Build: 59712M
- Platform: 32bit
- Version: 2.0RC2