Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication #88

Closed
rrrlasse opened this issue Apr 29, 2013 · 1 comment
Closed

Replication #88

rrrlasse opened this issue Apr 29, 2013 · 1 comment

Comments

@rrrlasse
Copy link
Contributor

In encode_int():

TIGHTDB_STATIC_ASSERT(std::numeric_limits<T>::is_integer, "Integer required");

If insertion can fail in replication, then insertion must fail in "core" insertion too, because behaviour in "core" and replication should be completely identical.

@ghost ghost assigned kspangsege Apr 29, 2013
@kspangsege
Copy link
Contributor

The static assert that you mention is just a compile time sanity check. With the current state of the code, the assert is not triggered, so all should be fine. Note that this assert cannot trigger at run time. It is there to help catch errors when the code is modified in the future.

I agree that replication mode must work identically to normal mode if at all possible.
If not possible, the differences should be few, well understood, and well documented.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants