Hello,
> https://github.com/glpi-project/docdev/issues/1
Agree :)
> - Improve the DBmysqlIterator
>
> https://github.com/glpi-project/glpi/pull/1096
>
> - suport COUNT(*)
I had in mind that count(*) is not the best choie for performances reasons. Am
I wrong?
> Other goal: add
Yes, me too
-Original Message-
From: Glpi-dev [mailto:glpi-dev-boun...@gna.org] On Behalf Of David DURIEUX
Sent: Sunday, October 02, 2016 3:25 PM
To: glpi-dev@gna.org
Subject: Re: [Glpi-dev] Eradicate SQL in GLPI
Le Sun, 2 Oct 2016 15:18:44 +0200
Remi Collet <fed...@famillecollet.
Le Sun, 2 Oct 2016 15:18:44 +0200
Remi Collet a écrit:
>On the road to allow GLPI to run on some other database engines, an
>intermediate goal is to eradicate SQL from the code.
>
>This will be useful whatever future choice will be.
>
>So:
>
>- all add / update / delete
On the road to allow GLPI to run on some other database engines, an
intermediate goal is to eradicate SQL from the code.
This will be useful whatever future choice will be.
So:
- all add / update / delete should be run using the appropriate
framework methods (CommonDBTM::add(), etc)
- add