Determining ids from a sequence with postgresql is not a problem but sqlite doesnt use such sequence objects, but for adding data into the database it is required to have the ids before insert. In sqlite the sequences are handled in a special system table sqlite_sequence which stores the last used value of each sequence. By manipulating this table it is possible to get unique sequence ids before inserting the records.
Another issue is that sqlite handles sorting of null fields the other way around than postgresql and does not support ORDER BY xxx DESC NULLS FIRST. Thats the reason why at the moment it isn't possible to synch with a sqlite based Tryton-server. (The slave can be sqlite based)
Updating of existing records is now possible. Furthermore a short screen cast is available on youtube to demonstrate the generic way of synching with Tryton servers. (http://www.youtube.com/watch?v=iAGP5fpdOAM)
Handling of function fields and default values is not implemented yet. Also MySQL has not been tested yet but there will also be the sequence issue.
For updating records prepared statements are not used but can be implemented if performance increase is needed. By now the write_many method only wraps the normal write method.
Big kudos for the cleaner code!
AntwortenLöschenI have some namespace issues I would like to comment. Which features are missing? Maybe it is time for a code review again?