developer.jelix.org is not used any more and exists only for
history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.
Opened 10 years ago
Closed 10 years ago
#1265 closed bug (fixed)
jCache::call() runs function again even if its results is cached for return values == false
Reported by: | bricet | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Jelix 1.2.1 |
Component: | jelix:utils | Version: | 1.2 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Documentation needed: | no | |
Hosting Provider: | Php version: |
Description
When using jCache::call(), we may lead to non-caching behaviour for calls to a function with specific args leading to a returned value == false (so 0, , array(), ...).
Even long-lasting functions may return such values ;)
May be we could restrict easily to === false (do all drivers return false when no cache value exists ?).
Having no special case would be the holy grail, but we should brake cache drivers API for that ...
Change History (2)
comment:1 Changed 10 years ago by laurentj
- Milestone set to Jelix 1.2.1
comment:2 Changed 10 years ago by laurentj
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
fixed https://bitbucket.org/jelix/jelix-1.2.x/changeset/a5b4b556c7b7