Excerpt from the Associated Press:
#--
Government secrecy by almost any measure is expanding and little is
being done to stop it, according to a coalition of 67 organizations
favoring greater openness
#---
Below is a link from OpenTheGovernment.org:
http://d
I'm guessing that the new enginebehaviour whereby a group by clause
must include all the fields that are selected is to follow a new SQL
standard, is that right?
Regardless of the source, why is this considered an improvement? It
seems to me to reduce my options for querying. I can imagine th
Mark Stanton wrote:
> I'm guessing that the new enginebehaviour whereby a group by clause
> must include all the fields that are selected is to follow a new SQL
> standard, is that right?
>
> Regardless of the source, why is this considered an improvement? It
> seems to me to reduce my options
On Sep 2, 2007, at 4:42 PM, Mark Stanton wrote:
> I'm guessing that the new enginebehaviour whereby a group by clause
> must include all the fields that are selected is to follow a new SQL
> standard, is that right?
>
> Regardless of the source, why is this considered an improvement? It
> seems t
Mark Stanton <> wrote:
> I'm guessing that the new enginebehaviour whereby a group by clause
> must include all the fields that are selected is to follow a new SQL
> standard, is that right?
>
> Regardless of the source, why is this considered an improvement? It
> seems to me to reduce my optio
Stephen the Cook wrote:
> Mark Stanton <> wrote:
>> I'm guessing that the new enginebehaviour whereby a group by clause
>> must include all the fields that are selected is to follow a new SQL
>> standard, is that right?
>>
>> Regardless of the source, why is this considered an improvement? It
>>
On Sep 2, 2007, at 7:58 PM, Ricardo Aráoz wrote:
> select EmployeeId, EmpName, sum(salary) ;
> from Employee ;
> group by EmployeeId
>
> This would have sense but it is easily done with :
To a human, perhaps, but to a database engine, there is no
constraint that the ID and name be a 1:1
Ed Leafe wrote:
> On Sep 2, 2007, at 7:58 PM, Ricardo Aráoz wrote:
>
>> select EmployeeId, EmpName, sum(salary) ;
>> from Employee ;
>> group by EmployeeId
>>
>> This would have sense but it is easily done with :
>
> To a human, perhaps, but to a database engine, there is no
> constraint
In Vfp6 I have a query which looks like
Parent Table Dpsa - Primary Key - UnikID
Child Table Saleadv - Foreign Key - UnikID
Table Buyer - Connected to Parent Table by field Bcode
For each record in the parent table I want one record back where the child
records will come as sum.
Select a.unikid,
The following advertisements are brought to you as a free service of the
ProFox mailing list. To enter your own ad, visit
http://leafe.com/adpost.html, and follow the instructions on that page.
There is no charge for posting an ad, and the only restriction is that all
ads must in some way relate
Vince Teachout wrote:
> Michael J. Babcock, MCP wrote:
>
>> Does this happen to anyone else? TB is constantly "forgetting" the saved
>> passwords I entered for my various email accounts, and it's a RPITA for me
>> to continually supply them. (If they were all the same, perhaps not pita,
>> but
11 matches
Mail list logo
