On Thu, Nov 24, 2011 at 12:42 AM, herman vierendeels
wrote:
> Hello Chris,
>
> On the next db-update release, following statements should be executed.
> But i do not know where to put them.
>
> ALTER TABLE entity_credit_account alter column language_code set default 'en';
> ALTER TABLE entity_cred
Hello Chris,
On the next db-update release, following statements should be executed.
But i do not know where to put them.
ALTER TABLE entity_credit_account alter column language_code set default 'en';
ALTER TABLE entity_credit_account ADD FOREIGN KEY (language_code)
REFERENCES language(code) ON D
On Tue, Nov 22, 2011 at 1:25 PM, herman vierendeels
wrote:
> Hi Chris,
>
> There already is a field language_code in entity_credit_account.
>
> But there is something i do not understand in
> sql/modules/Company.sql
> CREATE OR REPLACE FUNCTION entity_credit_save
> all parameters have a name stru
Hi Chris,
There already is a field language_code in entity_credit_account.
But there is something i do not understand in
sql/modules/Company.sql
CREATE OR REPLACE FUNCTION entity_credit_save
all parameters have a name structure like in_fieldname
except in_language
May i not change in_language t
Hi Herman;
On Tue, Nov 22, 2011 at 2:11 AM, herman vierendeels
wrote:
> Hello,
>
>
> Would it be wise,feasible to add field default_language to company?
>
> If not , could i add default_language as setting_key to table defaults ?
I would add it to entity_credit_account, and yes, this is importa
Hello,
Would it be wise,feasible to add field default_language to company?
If not , could i add default_language as setting_key to table defaults ?
Thanks,
Herman Vierendeels
--
All the data continuously generated i
