On Tue, 2002-11-05 at 09:10, Frederic Komp wrote: > > > 1. Is it possible to extend the (DB-)scheme so I can enhance my =3D > > > customer=3DB4s > > > information with arbitrary data like website, entry date or=20 > > structural =3D > > > address > > > info like street, zip, city, etc. ? > > where the customer's office resides. Is that what=20 > > "structural address" > > means? > > No, I meant extra fields to put the data in. It would need to be = > structured by > the database in order to reuse the information with other applications. = > That > means, you would have to tell SQL-Ledger respectively the PostgreSQL = > database > underneath it to have/use extra fields. This is more of a technical = > question... > but IMHO I think even to split the address information into street, ZIP, = > city, > etc. is a must for a well structured software...
I agree that this is a useful thing. A really ugly hack will be described below. On the other hand, it is GPL, you could do it yourself and submit a patch, you could hire someone to do it, or (I think the best idea) you could ask Dieter how much he would charge to do the changes. The reason I think asking Dieter to do the changes would be best would be because he knows all of the places in the code which will need to be changed to look for the zip field, the address_1, address_2 lines, et cetera. > > We have put extra information (hours, dog's name, wife's=20 > > birthday, kids > > names, and stuff like that) in the notes field. Then we look at that > > That does not work for applications to communicate... Agreed, it was a quick workaround on our part. Check out this hack. In the notes field, define each field as follows: Addr1(20t) Addr2(20t) Zip(15t) And stuff like that. The end of the record would be the carriage return/linefeed. Of course, all of the parsing software would be outside of SL at that point. I guess one might say, "When all you have is a hammer, everything looks like a nail." :-) have fun, rob
