Repository navigation
Conversation
|
Please add a test. |
|
@smalyshev: Tests added now The test for the inifile handler fails because this handler insert items even if the item already exists. I'm not a C developer so it would be the best merging this but leaving the bug open so another person can fix it. |
|
Hello guys, is there someone could review this ? |
|
@marc-mabe sorry for the long delay. Please fix the coding style issues after that it looks good for merge. |
|
@lstrojny : thank you for review! Updated coding style issues now |
There was a problem hiding this comment.
Is this really correct? Shouldn’t be the default case just throw some error?
There was a problem hiding this comment.
The default case should be impossible - it was copied from DBA_UPDATE_FUNC(flatfile)
- What should the message say on this case ?
- "Unknown return value %value% by %lib-function%" ?
- error, warning or notice?
There was a problem hiding this comment.
"Unknown return value" is fine. Warning seems appropriate to me.
|
After fixing the switch case, could you rebase and squash? |
…ected handlers are flatfile, inifile, qdbm and gdbm)
|
done! - updated the switch statements and squashed all commits together |
|
Merged into 5.5 and master. Cannot close it now as GitHub seems to be in trouble. |
|
Comment on behalf of lstrojny at php.net: Merged |
SHARP_MAGO_COMMIT named the head of Mago php#125 while it was under review. php#125 merged, so the pin now names its merge commit on Mago master. That commit also words an Any comparison operand in PHP#'s words in a .sharp file. The header it generates differs from this one only in the pin. ext/sharp/ └── sharp_unit.h <- SHARP_MAGO_COMMIT pins Mago 449377a, the merge of php#125
4 participants
removed warnings if dba_insert failed because of an already existing key.
fixed handlers are: