This is independant from the contact management refactoring that is
also going into 1.3, and is also happening along the same lines. For
security and logical reasons, the employees and external contacts are
kept separately in this voew. But the structures are fairly similar.
Best Wishes,
Chris T
On Tue, 6 Mar 2007, Chris Travers wrote:
> Hi all;
>
> I am looking at reactoring user information in 1.3. Here is my basic
> proposal:
>
> 1) Users are connected to three other tables: employee (for HR
> information), preferences (for their own preferences), and locations
> (for business locati
Hi all;
I am looking at reactoring user information in 1.3. Here is my basic proposal:
1) Users are connected to three other tables: employee (for HR
information), preferences (for their own preferences), and locations
(for business location).
The basic user table looks like:
create table db_
JD, Chris,
> The long and short of it is this. Core believes that data integrity
> belongs with your data,
Or, in less abstract terms, we expect that people will want to create plug-ins
and interoperability modules for LedgerSMB with other software. The best way
to make sure that extensions of
