Received: by 10.68.125.233 with SMTP id mt9mr51804pbb.5.1333135186194;
        Fri, 30 Mar 2012 12:19:46 -0700 (PDT)
X-BeenThere: schemaverse@googlegroups.com
Received: by 10.68.223.72 with SMTP id qs8ls6318599pbc.6.gmail; Fri, 30 Mar
 2012 12:19:45 -0700 (PDT)
Received: by 10.68.213.66 with SMTP id nq2mr19987pbc.13.1333135185779;
        Fri, 30 Mar 2012 12:19:45 -0700 (PDT)
Date: Fri, 30 Mar 2012 12:19:44 -0700 (PDT)
From: Abstrct <j...@saucetel.com>
To: schemaverse@googlegroups.com
Message-ID: <13431055.5.1333135184963.JavaMail.geo-discussion-forums@yngn14>
In-Reply-To: <7fbb17b3-7832-4757-95ca-f81590ad1fa7@h9g2000yqe.googlegroups.com>
References: <4e9521c8-0a1c-45c7-a119-5317781d2203@h3g2000yqe.googlegroups.com>
 <150c58fa-25ec-4623-8e2c-a75566137b6c@s18g2000vby.googlegroups.com>
 <c61e6c9e-a9eb-4d2a-855c-26ce7b1c8ae1@q8g2000yqa.googlegroups.com>
 <aa0ef318-e26a-41e0-a583-1aeb5c175367@do4g2000vbb.googlegroups.com> <10703801.185.1332445662736.JavaMail.geo-discussion-forums@vbyj26>
 <7fbb17b3-7832-4757-95ca-f81590ad1fa7@h9g2000yqe.googlegroups.com>
Subject: Re: Ships_In_Range :: Enemy Health
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_3_21395016.1333135184961"

------=_Part_3_21395016.1333135184961
Content-Type: multipart/alternative; 
	boundary="----=_Part_4_16747070.1333135184961"

------=_Part_4_16747070.1333135184961
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

ahahahaha sorry about that! Totally all my fault. I thought I was being 
helpful D:

I will revive any ships in the system that were killed by friendly fire.

Is this feature helpful at all or should the view be changed back to 
excluding all of your own ships?

On Friday, 30 March 2012 14:38:57 UTC-4, MassConfusion wrote:
>
> Well, I just noticed a fun fact! 
>
> Somewhere in the last iteration or so the Ships_In_Range view now 
> shows friendly ships as well as enemy ones, consequently, my script 
> has literally whacked every single one of my own ships. 
>
>
> On Mar 22, 2:47 pm, Christopher Browne <cbbro...@gmail.com> wrote: 
> > On Monday, 23 January 2012 20:04:50 UTC-5, Abstrct wrote: 
> > 
> > > The view is still slow as hell but, ya, working on it. 
> > 
> > I have a suggested patch out there to improve this view... 
> > 
> > Basic idea being that if you add the player ID to the ships_near_ships 
> > table,  it becomes way more efficient to filter it down to just *my* 
> ships. 
> > 
> > I added columns for both players (player + opponent), which may be 
> > overkill.  Perhaps it suffices to specify the one player.


------=_Part_4_16747070.1333135184961
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

ahahahaha sorry about that! Totally all my fault. I thought I was being helpful D:<div><br></div><div>I will revive any ships in the system that were killed by friendly fire.</div><div><br></div><div>Is this feature helpful at all or should the view be changed back to excluding all of your own ships?<br><br>On Friday, 30 March 2012 14:38:57 UTC-4, MassConfusion  wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">Well, I just noticed a fun fact!
<br>
<br>Somewhere in the last iteration or so the Ships_In_Range view now
<br>shows friendly ships as well as enemy ones, consequently, my script
<br>has literally whacked every single one of my own ships.
<br>
<br>
<br>On Mar 22, 2:47&nbsp;pm, Christopher Browne &lt;<a>cbbro...@gmail.com</a>&gt; wrote:
<br>&gt; On Monday, 23 January 2012 20:04:50 UTC-5, Abstrct wrote:
<br>&gt;
<br>&gt; &gt; The view is still slow as hell but, ya, working on it.
<br>&gt;
<br>&gt; I have a suggested patch out there to improve this view...
<br>&gt;
<br>&gt; Basic idea being that if you add the player ID to the ships_near_ships
<br>&gt; table, &nbsp;it becomes way more efficient to filter it down to just *my* ships.
<br>&gt;
<br>&gt; I added columns for both players (player + opponent), which may be
<br>&gt; overkill. &nbsp;Perhaps it suffices to specify the one player.</blockquote></div>
------=_Part_4_16747070.1333135184961--

------=_Part_3_21395016.1333135184961--