On Thu, Sep 07, 2000 at 10:23:57AM -0300, The Hermit Hacker wrote:
> BTW, what do you mean by 'went away'? crashed, or just hung there?
Stopped using CPU, stopped responding to signals (except in the end -9),
and when I did finally kill it (the following day, to give it chance to
do what it was
On Thu, Sep 07, 2000 at 02:11:38PM +0100, Oliver Smith wrote:
> However, when I did that, postgres went away. I'll give your idea a try,
> it looks quite promising.
I still found this took quite a long time to process the query. So - I created
the four views, silver, elec, gold, plat
On Wed, Sep 06, 2000 at 10:52:34PM -0300, The Hermit Hacker wrote:
> SELECT
> stone_name, st.stone_uid, stone_modifies, stone_difficulty, stone_cost,
> silver.jtyp_name AS silver_name, (silver.metal_cost + stone_cost) AS Expr1,
> silver.jcombo_stats AS silver_stats,
> elec.jtyp_name AS el
> OTOH, I'm not 100% sure what you're trying to get out
> from this query, I'd have expected that it would be, using
> these metals on this stone gives you this result, but since
> the types of jewelery I get are different on the same row
> of output, I'm a little confused.
Each stone gives a spe
In order to explore some postgres performance options with table
collation, I decided to use a little experimental dabase to try out
some of the options I saw. What I want to create queries to combine
data from 2+ tables into individual rows.
So - being a bit of an EQ player, I cobbled together a
