ECTED]
On Behalf Of george young
Sent: Tuesday, November 08, 2005 6:15 PM
To: pgsql-sql@postgresql.org
Subject: Re: [SQL] Design question: Scalability and tens of thousands of
On Thu, 3 Nov 2005 09:58:29 -0800
"zackchandler" <[EMAIL PROTECTED]> threw this fish to the penguin
On Thu, 3 Nov 2005 09:58:29 -0800
"zackchandler" <[EMAIL PROTECTED]> threw this fish to the penguins:
> I'm designing an application that will allow users to create custom objects
> on the application level. A custom object can have zero or more attributes.
> Attributes can be one of 5-10 types (e
> On Nov 4, 2005, at 9:47 AM, [EMAIL PROTECTED] wrote:
>
>> The problem is I am very concerned about scalability with having a
>> different
>> table created for each custom object. I want to design to site to
>> handle
>> tens of thousands of users. If each user has 3-5 custom objects the
>> data
On Nov 4, 2005, at 9:47 AM, [EMAIL PROTECTED] wrote:
The problem is I am very concerned about scalability with having a
different
table created for each custom object. I want to design to site to
handle
tens of thousands of users. If each user has 3-5 custom objects the
database would hav
On Nov 4, 2005, at 2:58 , zackchandler wrote:
The problem is I am very concerned about scalability with having a
different
table created for each custom object. I want to design to site to
handle
tens of thousands of users. If each user has 3-5 custom objects the
database would have to ha
Hi everybody. Quick question:
I'm designing an application that will allow users to create custom objects
on the application level. A custom object can have zero or more attributes.
Attributes can be one of 5-10 types (ex. String, Number, List, Date, Time,
Currency, etc...). This will allow user
