Hello, I am currently working on two patches that will make it easier to create python modules adding a new backend to tryton:
- https://tryton-rietveld.appspot.com/33951002/ This patch moves the handling of the SQL type of the tryton fields to the backend. In order to have a kind of lingua franca between tryton and the backend we specify on the field the "abstract" SQL types it wants to use (a M2O will use an INTEGER, a TimeDelta an INTERVAL, and so on). - https://tryton-rietveld.appspot.com/26231002/ This patch uses the abstract SQL types to create the column in the backend instead of the raw SQL type that was used before. You can see those patch in action in the following patch adding a postgis backend which inherits almost everything from the postgres backend: https://codereview.appspot.com/322730043/ We wonder if there is some kind of interest to make this backend supported by community or if we should keep it in the B2CK realm. According to me we should definitely support this backend (I personally know ∞-time more people that would use this backend then the mysql one). And this last remarks makes me wonder if we shouldn't make of the mysql backend this kind of python package (supported by the community but not release critical at all). What are your thoughts about it? -- Nicolas Évrard - B2CK SPRL E-mail/Jabber: nicolas.evr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/ -- You received this message because you are subscribed to the Google Groups "tryton-dev" group. To view this discussion on the web visit https://groups.google.com/d/msgid/tryton-dev/20170320173428.acm6m2xzt3idjkcf%40localhost.localdomain.
