Tuesday, November 6. 2012Data from different databasesTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Is this common pool of data meant to be read-only to all of those users or read-write to a substantial number of them? If read-only, that gives you a lot more options to work with. It's mostly read-only. Yes we have a number of choices, and we'll be able to manages this, but none of them are terribly attractive. Consider this problem multiplied a couple of thousand times. If my client had a million clients instead of 500 or so to deal with, how would we manage this? I hope we will soon have PostgreSQL Foreign Data Wrappers to help you solve that issue, someday even with read/write access... They are going to have to get really really good for us to be able to use them. These tables are used in some quite complex and timing-critical joins. We have the same issue here except we use a new schema for each project. <br /> |
My Links etcBlog AdministrationCalendar
QuicksearchArchivesCategories |
|||||||||||||||||||||||||||||||||||||||||||||||||