By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,789 Members | 1,432 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,789 IT Pros & Developers. It's quick & easy.

Modular application needing additional columns?

P: n/a
I'm writing an application with PostgreSQL as the database which I would
like to be as modular as possible. It will have various modules, each of
which will have their own database schema. A module with users might
define a user table, but an RPG module would want the user table to have
a column for money. I don't want the users module to know about the RPG
module beforehand, so it can't have the money column. Should the RPG
module subclass the user table and make other modules use its subclass
from now on? Should it just add the column when it's installed? What
have others done?

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 22 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.