Re: [GENERAL] explosion of tiny tables representing multiple

2006-11-05 Thread Martijn van Oosterhout
On Fri, Nov 03, 2006 at 08:25:25PM +, Benjamin Weaver wrote: > Dear Martijn, > > Wow, didn't know about arrays. Did lots of sql, but, as I think about it, > that was 7 years ago, and we didn't know about arrays then > > Are their performance problems with arrays? We will not likely be work

Re: [GENERAL] explosion of tiny tables representing multiple

2006-11-04 Thread Benjamin Weaver
Dear Martijn, Wow, didn't know about arrays. Did lots of sql, but, as I think about it, that was 7 years ago, and we didn't know about arrays then Are their performance problems with arrays? We will not likely be working with more than 50,000 - 100,000 records. Ben In message <[EMAIL PROTE

Re: [GENERAL] explosion of tiny tables representing multiple fields--Is this necessary?

2006-11-03 Thread Martijn van Oosterhout
On Thu, Nov 02, 2006 at 04:36:49PM +, Benjamin Weaver wrote: > Dear PostGreSQL experts, > > > I am working with text objects. A text object will have lots of fields that > are potentially multiple. There may be more than one author, more than one > modern editor, more than one edition numbe

[GENERAL] explosion of tiny tables representing multiple fields--Is this necessary?

2006-11-03 Thread Benjamin Weaver
Dear PostGreSQL experts, I am working with text objects. A text object will have lots of fields that are potentially multiple. There may be more than one author, more than one modern editor, more than one edition number, etc. These potentially multiple fields are, in my schema, nothing more th