Mr. Klauschen,
> I try to find a way to enter a list of items into my
> database , of which the size should be flexible.
> I then would like perform queries on that list in
> a way, that the whole list is retrieved, when the
> query's items are found to be in that list.
> Thanks for any help,
Ca
Folks,
Also, any reviews on foriegn-language SQL or database books (in the
appropriate language) would be appreciated.
-Josh
__AGLIO DATABASE SOLUTIONS___
Josh Berkus
Complete information technology [EMAIL PROTECTED]
Kevin,
> After doing so, you'll find that postgres actually crashes when you
> try
> to insert a vote into the uservote table. That's the one that has me
> looking at the costs involved with migrating to Oracle.
And you think that Oracle is entirely free of bugs? ;-)
At least here, you can ge
Frederick,
> The problem is that I do not know what kind of
> attributes the user wants to enter. So I do not
> want to create a table with attributes like
> "Hometown", "eye color" , etc. The user should just
> enter what he likes to.
This is actually a common SQL issue. If I knew a good SQL b
> And you think that Oracle is entirely free of bugs? ;-)
Yes, but they'd be exciting technology-oriented e-business enabled bugs!
> Still, I understand your frustration.
Thanks... It's just frustrating that the bug is on something so basic,
which makes it both hard to code around and hard
He is probably thinking about arrays. contrib/array, contrib/intarray
could be worth to see.
Oleg
On Mon, 24 Sep 2001, Josh Berkus wrote:
> Mr. Klauschen,
>
> > I try to find a way to enter a list of items into my
> > database , of which the size should be flexible.
> > I then would like
Kevin Way wrote:
> I'm unemployed at the moment and this is a pet project, so I can't offer
> much in the way of financial compensation, but I'll start the bidding at
> $50 donation in your name to your choice of the EFF, the Red Cross, or the
> American Cancer Society, in return for a fix. (If n
Baldvin,
> Probably the chances for a prize went... :-(( However, is there
> still a shortage of blod???
Last I checked, the American Red Cross does not want your blood right
now -- they want it two weeks from now. Currently blood stores are
full, but they get depleted pretty fast. Of course,
hi.
I still go on looking for query time.
I get a question!
explain is a command that estimate cost of query time ok, but I don't
know how is the time.
for example:
mybase=> explain select * from tabla1;
NOTICE: QUERY PLAN:
Seq Scan on tabla1 (cost=0.00..1.06 r
> -- I don't think that I only found a minor bug compared to
> -- the other you wrote in your last letter: the backend crash
> -- is caused by the same CHECK constraint in the child table.
Oooh, my bad. I should run your scripts before assuming I know how
they fail.
> -- However, for you withou
Alex Pilosov <[EMAIL PROTECTED]> writes:
> I'm going to CC this to -hackers, maybe someone will shed a light on the
> internals of this.
It's not unintentional. See
http://www.ca.postgresql.org/users-lounge/docs/7.1/postgres/explicit-joins.html
regards, tom lane
--
-- Hi Kevin, and everyone!
--
-- I don't think that I only found a minor bug compared to
-- the other you wrote in your last letter: the backend crash
-- is caused by the same CHECK constraint in the child table.
--
-- However, for you without time to analyzing Kevin's huge
-- scheme, here is th
Kovacs Baldvin wrote:
> Hi everybody!
>
> I tried, and it works: the current CVS version really runs
> happily the query what sent to heaven our 7.1 version of the
> backend.
>
> Kevin: your original complex schema also runs smoothly.
>
> Thanks for our mindful developers!
>
> Regards,
> Baldvin
>
On Mon, 24 Sep 2001, Alex Pilosov wrote:
> On Sun, 23 Sep 2001, Stephan Szabo wrote:
>
> > On Sun, 23 Sep 2001, Alex Pilosov wrote:
> >
> > Postgres treats join syntax as an explicit definition of what order to
> > joins in. So, I'd guess it sees the first as: do the LOJ and then join
> > that
What version are you trying this script on? I'm not
seeing a crash on my 7.2 devel system (and the update occurs).
On Mon, 24 Sep 2001, Kovacs Baldvin wrote:
> -- Hi Kevin, and everyone!
> --
> -- I don't think that I only found a minor bug compared to
> -- the other you wrote in your last le
Hi everybody!
I tried, and it works: the current CVS version really runs
happily the query what sent to heaven our 7.1 version of the
backend.
Kevin: your original complex schema also runs smoothly.
Thanks for our mindful developers!
Regards,
Baldvin
I think Jan wrote:
> Sorry, I missed
On Mon, Sep 24, 2001 at 03:23:13PM -0400, Jan Wieck wrote:
>
> It help's saving life! Using the victims for that purpose
> isn't abuse. It is turning grief, anger and sadness into
> help and hope.
>
> Let blood become "Open Source". Give it for free and you'll
> ge
17 matches
Mail list logo
