On Tue, Jun 26, 2012 at 12:32 PM, Cédric Krier <[email protected]>wrote:
> On 26/06/12 12:16 +0200, Rom1 wrote: > > On Tue, Jun 26, 2012 at 10:10 AM, Cédric Krier <[email protected] > >wrote: > > > > > On 25/06/12 10:10 -0700, sampac wrote: > > > > I think we should store only one number AND a type. > > > > Depending on the type, we can call different methods to interpret the > > > > account number differently : validate it, extract the bank code, the > > > > branche code, the account code,... > > > > > > I'm pretty sure that we must store all the different formats of an > > > account. > > > > > > > I don't know what are the information needed for each country. > > Do you think, we also need to store the country information (needed for > the > > iban) or we juste need the Iban (that contains the country) ? > > If so, we could calculate the iban with an on_change on the other fields, > > otherwise if the account is a RIB I could calculate the IBAN but I don't > > know how I could go further. > > I mean the "Bank Account" Model must contains a list of "Account Number" > with a type and the corresponding required fields. > what do you mean a "list", a O2M of item with a char and a type, or just 4-5 char on the bank account table? How do you deal with required fields as it is different for each country? You still havn't answered my question, do you think we need to store the country? (This way for a french account we won't need to say it's a RIB). > Indeed I don't care about computing some of them or not, that's just a > minor feature. The important thing is the way data are stored. > > For you, maybe, but for the user this is a key feature. :) > -- > Cédric Krier > > B2CK SPRL > Rue de Rotterdam, 4 > 4000 Liège > Belgium > Tel: +32 472 54 46 59 > Email/Jabber: [email protected] > Website: http://www.b2ck.com/ > -- -- [email protected] mailing list
