[tryton-dev] Un-assigned Tryton issue tracker requests
Created ID Activity Title === bug 2 weeks ago 4740 2 weeks ago tryton doesn't find icons on Ubuntu bug 2 months ago 4643 2 months ago 'NoneType' object has no attribute 'on ... bug 2 months ago 4603 2 months ago 'Mono' is not in list bug 3 months ago 4582 3 months ago Display datetime before epoch on windows bug 4 months ago 4505 4 months ago tryton client crashes when hitting clo ... bug 6 months ago 4359 6 months ago Windows client error when image size i ... To view or respond to any of the requests listed above, visit the URL https://bugs.tryton.org/ and click on "Show Unassigned". Do NOT respond to this message.
Re: [tryton-dev] Database schema name limit
On 23 May 11:01, Mathias Behrle wrote: > * Cédric Krier: " [tryton-dev] Database schema name limit" (Thu, 21 May 2015 > 17:52:57 +0200): > > > Hi, > > > > I'm facing a limitation with how trytond generate the table name for a > > ModelSQL. Databases have different length limitation for schema name. > > For example, > > PostgreSQL has the limit to 64 when Oracle has the limit to 30 > > (yes I'm working on an Oracle backend). > > > > I don't want that we change our naming convention because it is quite > > good and reducing the name will just bring a lot in readability. > > And we will be forced to use the least common constraint. > > > > So my idea is to have a configuration section which will provide the > > table name to use for a Model. > > > > Example: > > > > [table] > > account.invoice.payment_term.line.relativedelta = acc_inv_pt_l_reldelta > > account.payment.sepa.message = acc_payment_sepa_msg > > > > Of course such configuration could not be modified once a database has > > been created (or the table should be renamed). > > > > Side effect, it could also be used to fix naming conflict between 2 > > unrelated module (at the database level not Model.__name__). > > > > What do you think? > > The backside of this translation table is, that you have to know beforehand > all > tables in your database, before you install them and that it has to be done > manually. Yes but any way, any *real* production installation will require to customize the database schema. I always thought that Tryton will never generate the perfect schema but only a minimal working schema. > What about a configuration option 'oracle_compatibility = True', that will > slug > the ususal names in a reproducible way? The problem is not oracle. The problem is the limitation that all databases have. But if you have a better solution, I will be graceful to evaluate. For example, a good algorithm to generate size compatible from Model name. -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
Re: [tryton-dev] Database schema name limit
* Cédric Krier: " [tryton-dev] Database schema name limit" (Thu, 21 May 2015 17:52:57 +0200): > Hi, > > I'm facing a limitation with how trytond generate the table name for a > ModelSQL. Databases have different length limitation for schema name. > For example, > PostgreSQL has the limit to 64 when Oracle has the limit to 30 > (yes I'm working on an Oracle backend). > > I don't want that we change our naming convention because it is quite > good and reducing the name will just bring a lot in readability. > And we will be forced to use the least common constraint. > > So my idea is to have a configuration section which will provide the > table name to use for a Model. > > Example: > > [table] > account.invoice.payment_term.line.relativedelta = acc_inv_pt_l_reldelta > account.payment.sepa.message = acc_payment_sepa_msg > > Of course such configuration could not be modified once a database has > been created (or the table should be renamed). > > Side effect, it could also be used to fix naming conflict between 2 > unrelated module (at the database level not Model.__name__). > > What do you think? The backside of this translation table is, that you have to know beforehand all tables in your database, before you install them and that it has to be done manually. What about a configuration option 'oracle_compatibility = True', that will slug the ususal names in a reproducible way? -- Mathias Behrle MBSolutions Gilgenmatten 10 A D-79114 Freiburg Tel: +49(761)471023 Fax: +49(761)4770816 http://www.m9s.biz UStIdNr: DE 142009020 PGP/GnuPG key availabable from any keyserver, ID: 0x8405BBF6 pgp4KUq7yLfz8.pgp Description: Digitale Signatur von OpenPGP
[tryton-dev] Database schema name limit
Hi, I'm facing a limitation with how trytond generate the table name for a ModelSQL. Databases have different length limitation for schema name. For example, PostgreSQL has the limit to 64 when Oracle has the limit to 30 (yes I'm working on an Oracle backend). I don't want that we change our naming convention because it is quite good and reducing the name will just bring a lot in readability. And we will be forced to use the least common constraint. So my idea is to have a configuration section which will provide the table name to use for a Model. Example: [table] account.invoice.payment_term.line.relativedelta = acc_inv_pt_l_reldelta account.payment.sepa.message = acc_payment_sepa_msg Of course such configuration could not be modified once a database has been created (or the table should be renamed). Side effect, it could also be used to fix naming conflict between 2 unrelated module (at the database level not Model.__name__). What do you think? -- Cédric Krier - B2CK SPRL Email/Jabber: cedric.kr...@b2ck.com Tel: +32 472 54 46 59 Website: http://www.b2ck.com/
