Re: [GENERAL] Dynamic data model, locks and performance

2010-08-03 Thread ChronicDB Community Team
This example is certainly a workable situation. However it does require understanding the constraints of an ALTER TABLE statement and manually developing appropriate scripts. The update model offered my ChronicDB accounts for schema changes of considerable complexity, such as merging fields,

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-30 Thread Andreas Joseph Krogh
On 07/29/2010 05:15 AM, Pierre Thibault wrote: 2010/7/28 Craig Ringer cr...@postnewspapers.com.au mailto:cr...@postnewspapers.com.au On 29/07/10 07:06, Pierre Thibault wrote: I doubt anyone can make any useful recommendations without a more complete explanation of what you're

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-30 Thread John R Pierce
On 07/30/10 1:08 PM, Andreas Joseph Krogh wrote: You might want to take a look at TopicMaps, http://www.topicmaps.org/ One of the greatest topicmap-engines is opensource: http://www.ontopia.net/ Huh, visited both those sites, and I still have no idea what TopicMaps actually are. -- Sent

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-30 Thread Andreas Joseph Krogh
On 07/30/2010 10:20 PM, John R Pierce wrote: On 07/30/10 1:08 PM, Andreas Joseph Krogh wrote: You might want to take a look at TopicMaps, http://www.topicmaps.org/ One of the greatest topicmap-engines is opensource: http://www.ontopia.net/ Huh, visited both those sites, and I still have no

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-29 Thread Yeb Havinga
Pierre Thibault wrote: Hello people of the Postgresql world! I am wondering if Postgresql would a great choice for my database needs. I would like to create a db with dynamic data model. I would like to be able to add tables and columns to existing tables while other queries are running. It

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-29 Thread Craig Ringer
On 29/07/10 22:36, Pierre Thibault wrote: Why so? This is something expected by a database used in a constant integration environment. Maybe I did not expressed myself very well. Users are not changing their models all the time. They create new models which mean create new tables and from

[GENERAL] Dynamic data model, locks and performance

2010-07-28 Thread Pierre Thibault
Hello people of the Postgresql world! I am wondering if Postgresql would a great choice for my database needs. I would like to create a db with dynamic data model. I would like to be able to add tables and columns to existing tables while other queries are running. Will Postresql be able to

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-28 Thread Craig Ringer
On 29/07/10 07:06, Pierre Thibault wrote: Hello people of the Postgresql world! I am wondering if Postgresql would a great choice for my database needs. I would like to create a db with dynamic data model. I would like to be able to add tables and columns to existing tables while other

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-28 Thread Pierre Thibault
2010/7/28 Craig Ringer cr...@postnewspapers.com.au On 29/07/10 07:06, Pierre Thibault wrote: I doubt anyone can make any useful recommendations without a more complete explanation of what you're trying to achieve and why you want to do what you have described. Thank you Craig, Yes, I was

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-28 Thread Peter Hunsberger
On Wed, Jul 28, 2010 at 10:15 PM, Pierre Thibault pierre.thibau...@gmail.com wrote: What I would like to do is enable users to create their own data model. Enable them to create a model and make it evolve. For example, it would be cool to create a model to represent car adds. Then, the

Re: [GENERAL] Dynamic data model, locks and performance

2010-07-28 Thread Craig Ringer
On 29/07/10 11:15, Pierre Thibault wrote: What I would like to do is enable users to create their own data model. Then, really, SQL databases aren't wonderful for your needs. You can use them for dynamic, user-defined schema, but you'll always be swimming up hill. I thought about using a