fix: Récupérer l'opération active depuis la table operations
- Corrige l'erreur SQL 'Unknown column fk_operation in users' - L'opération active est récupérée depuis operations.chk_active = 1 - Jointure avec users pour filtrer par entité de l'admin créateur - Query: SELECT o.id FROM operations o INNER JOIN users u ON u.fk_entite = o.fk_entite WHERE u.id = ? AND o.chk_active = 1
This commit is contained in:
0
cron/batiments.md
Normal file → Executable file
0
cron/batiments.md
Normal file → Executable file
0
cron/doc/CHANGELOG.md
Normal file → Executable file
0
cron/doc/CHANGELOG.md
Normal file → Executable file
0
cron/doc/README.md
Normal file → Executable file
0
cron/doc/README.md
Normal file → Executable file
0
cron/doc/documentation.xlsx
Normal file → Executable file
0
cron/doc/documentation.xlsx
Normal file → Executable file
0
cron/dump-adresses-202511061203.sql
Normal file → Executable file
0
cron/dump-adresses-202511061203.sql
Normal file → Executable file
0
cron/init_batiments.sql
Normal file → Executable file
0
cron/init_batiments.sql
Normal file → Executable file
0
cron/test_batiments_35.sh
Normal file → Executable file
0
cron/test_batiments_35.sh
Normal file → Executable file
0
cron/traite_adresses.sh
Normal file → Executable file
0
cron/traite_adresses.sh
Normal file → Executable file
0
cron/traite_batiments.sh
Normal file → Executable file
0
cron/traite_batiments.sh
Normal file → Executable file
0
cron/traite_batiments.sql
Normal file → Executable file
0
cron/traite_batiments.sql
Normal file → Executable file
0
cron/traite_osm.sh
Normal file → Executable file
0
cron/traite_osm.sh
Normal file → Executable file
Reference in New Issue
Block a user