Adding an ID field should not affect openser as most modules bind by column
name. I had to do the same to a some of my tables.
-Sumeet
From: Mike Williams <[EMAIL PROTECTED]>
To: [email protected]
Subject: [Devel] modifying the database structure
Date: Fri, 26 May 2006 11:53:20 -0400
I was wondering if modifying the database structure would have some kind of
ill effects on the operation of OpenSER. For instance, the domain table has
two columns, domain and last_modified. Having the value column also be the
primary key is making it difficult for me to use it in any object
relational
mapping code, specifically in ruby on rails. Likewise, I can't do any
foreign
key constraints at the database level, so consistency checking is zero. I
would like to add an id field instead and just specify that domain is
unique.
I would like to release some source code for a very basic web interface I
am
working on, but I don't want to do so if I will immediately receive a
million
emails about how broken it is.
Often, I consider redoing the database structure completely, and then
mapping
views from it for OpenSER's use. This would also alleviate some of the
problems I'm having with integrating OpenSER and Asterisk effectively
without
adding a million columns to the subscriber table. However, I also don't
want
to break the modularity that OpenSER currently has.
Any advice?
---Mike
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
