[odb-users] Variable name conflict in generated code

Boris Kolpackov boris at codesynthesis.com
Fri Sep 15 09:30:07 EDT 2017

Dieter Govaerts <dieter.govaerts at bricsys.com> writes:

> Oh, seems to be working pretty well already in my case in 2.4.0 on
> sqlite except for that small error. I do persist, update and a simple
> query by Key::name on KeyValue and experienced no problems so far.

That's good to hear.

> Would you advice against using object pointer as id with 2.4.0?

There are a lot of moving parts and optional features in ODB that
need to be carefully reviewed and analyzed WRT interaction with
this feature before we can call it "officially" supported.

But if it compiles and you have tested it to be working in the
scenarios that you need, then I don't see a reason why not to
use it.

If you would like, I can build a pre-release binary with the
compilation issue fixed (I've already committed the fix).


More information about the odb-users mailing list