What I think I am going to do is design the table structure for my db and then use a trigger to update the otrs tables(kept separate) when necessary. If I mixed the tables then I could potentially run into issues when I do an upgrade of otrs or if I need to change something on my end down the line. Keeping them separate seems to make more sense to me right now.
On Fri, Jun 24, 2011 at 8:15 PM, Joshua Tolley
<eggyknap@gmail.com> wrote:
On Thu, Jun 16, 2011 at 08:50:30AM -0400, matty jones wrote:
> I am going to be setting up OTRS, a help desk application, and the backend
> is going to be Postgres, along with this I need to create
> a separate application to track whether or not a customer has a service
> contract with us and the type of service contact. The question I have is
> that the service application will have a table that stores the customer's
> contact information, and OTRS also has this table, is there a way I can
> share this table between these two applications?
Do the two applications have the same concept for this table? In other words,
do they both expect the same table structure, field names, data types, field
order, indexing, etc.? If not, it will be pretty tough to get them to share
the table.
--
Joshua Tolley / eggyknap
End Point Corporation
http://www.endpoint.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAk4FKK0ACgkQRiRfCGf1UMPvfACeJTmnF2cYYIK3e0uutXjXxR5a
L10AoJxAIRr9mYGDsuSVNocbjMCCQa31
=XUCW
-----END PGP SIGNATURE-----
