| From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
|---|---|
| To: | Chris Angelico <rosuav(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL limitations question |
| Date: | 2012-07-13 16:40:40 |
| Message-ID: | CABs1bs3uu+HkzRC2DKZEVg7mf2AGsMsuitGxFu-6oTJa0CWmHQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jul 13, 2012 at 12:05 AM, Chris Angelico <rosuav(at)gmail(dot)com> wrote:
> On Fri, Jul 13, 2012 at 4:14 AM, Bartosz Dmytrak <bdmytrak(at)gmail(dot)com> wrote:
>> I think there should be an explanation what *unlimited* really means.
>>
>
> Unlimited doesn't mean you can have infinite of something, but just
> that that specific attribute doesn't have its own limit. For instance,
> if I fly to England, I am allowed to carry as much sheet music with me
> as I like ("unlimited"), but there are weight limits on my total
> baggage. In theory, I could calculate exactly how many bars of music I
> could fit, at the tightest font size I can reasonably use, on the
> lightest paper, etc, etc, and thus figure out that the airline limits
> me to X amount of sheet music; but there's no actual limit on sheet
> music.
Wait, are you suggesting Olive Garden doesn't *actually* offer
unlimited breadsticks?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Angelico | 2012-07-13 16:48:01 | Re: PostgreSQL limitations question |
| Previous Message | Chris Travers | 2012-07-13 12:57:04 | Re: WITH RECURSIVE question |