On Tue, Jun 26, 2012 at 2:41 PM, Cédric Krier <[email protected]> wrote:
> On 26/06/12 14:25 +0200, Rom1 wrote: > > On Tue, Jun 26, 2012 at 12:32 PM, Cédric Krier <[email protected] > >wrote: > > > I mean the "Bank Account" Model must contains a list of "Account > Number" > > > with a type and the corresponding required fields. > > > > I'm not sure, I understood correctly. What do you have in the O2M ? account ->RIB ->IBAN ->any account number or account ->bank code ->branch code -> account number -> key > > > > 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? > > A One2Many > > > How do you deal with required fields as it is different for each country? > > For now, from all the different kind of bank account number I know, a > simple char field is enough. > > > 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). > > I think a "Bank account" should have an address but it should be > investigated to know what is the common form for it. > > I don't know for other countries, but in France, you have a repos for each bank code/branch code with the address, you don't specify the address each time you enter a new RIB, as it is the same for all the customer of the branch. I suppose it's the same wherever you have a branch code. But you'll need the country first the restrict the search, because branch code are only unique per country. > > 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. :) > > Early overfeatured requirements is the best way to fail. > > thank you. > -- > 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
