DB Login has impact on "RequestLiveness"

DB Login has impact on "RequestLiveness"

Post by Sylvain St.Germai » Tue, 26 Nov 1996 04:00:00



I am confused...
From day one I was logging into my system (D1, SybaseSQLAny 5.01) with a
user id and password that were fixed and setup at design time in the
TDatabase object.

But since I've implemented my login dialog the system behave differently
for the same user... even if the user permisions have not changed nor
the system itself other than the way I login to it.

Here it is.
The user I am talkin about HAD since the begining the following
permissions:
grant select, insert, delete, update, references for all the tables.
This has never been changed.

Since the login dialog thing... BDE is complaining about the token
'Effort' on line 2 (of the query below) when it creates the
form...

select e.MembreClient, e.CodeService, e.DateJour, e.Duree, e.Note
from dba.Effort e where (e.MembreEmploye like (:CurEmploye)) order by 1

The previous Query used to have RequestLive set to true, but since that
login thing I must set RequestLive to False in order to make it work,
obviously I cannot anymore modify the result set...

Also, I was under the implression that one of the rule to get a live
result set was 'No Order By Clause'  But it was working perfectly...
This is confusing...

Question: Could the way I login onto the database requires the query's
RequestLive property be set to False... Is this possible or am I missing
something?

As usual, any help/experience/joke much appreciated.

Reagrds,
Sylvain.

 
 
 

1. Having "HAVING" problems with GROUP BY.

My query is quite complex, and it also not working properly! *g*
From 2 tables, I am selecting records grouped by player_id where a certain
number of conditions are met (ie: date_caught, etc.)
I need to perform 2 GROUP BYs.  1 to ensure that the SUM of the
actual_points is within a certain value, and the 2nd to ensure that each
player has at least 4 entries.

I am only choosing the top four, which isn't a problem for players with 4 or
more entries, but the group by is NOT working for players who have less than
4 entries.  It is NOT leaving out the players with 3 or less
entries......ANY HELP WOULD BE GREATLY APPRECIATED.

Here's the SQL (i've tried to snip it as much as I could....):

SELECT player_id , ROUND(SUM(actual_points)) as points FROM ( SELECT * FROM
(SELECT player_id
, actual_points
, row_number() OVER (PARTITION BY player_id ORDER BY actual_points desc)
rank
, date_caught
FROM (SELECT *
FROM (SELECT ce.entry_id
, ce.date_caught as date_caught
, ce.actual_points as actual_points
, ce.player_id as player_id
FROM fantasy_entries ce )
UNION
SELECT *
FROM( SELECT ce.entry_id
, ce.date_caught as date_caught
, ce.actual_points as actual_points
, players.player_id as player_id
FROM catch_entries ce, dogfish.players
WHERE ce.pin = players.pin )
)
)
WHERE rank < 5
AND player_id IN ( SELECT *
FROM (SELECT player_id
FROM fantasy_entries
UNION
SELECT *
FROM (SELECT player_id
FROM (SELECT pl.player_id as player_id
, ce.pin
FROM players pl
, catch_entries ce
WHERE pl.pin = ce.pin)
)
)
GROUP BY player_id HAVING COUNT(actual_points) = 4) /*(when this is '> 0',
it works okay, it just doesn't filter the players with more than 4
entries)*/
)
GROUP BY player_id HAVING SUM(actual_points) BETWEEN 0 AND 2800
ORDER BY points desc

Thanks in advance....I really appreciate any insight.  (I've been fighting
with this for a week!)
--
Joseph Ranseth - Webmaster
World Cup Fishing
http://www.worldcupfishing.com

2. WIN.INI setting

3. max of ("...","...","..")

4. US-VA-DC Nextstep Developers

5. "Zero Impact" SQL Monitor

6. US-CA-Product Support Specialist-Oracle PL SQL, Forms, Unix, NT

7. YEAR 2000 "BUG": IMPACT ON DATABASES AND DBM

8. Help!- Transfer of 40MGs

9. Impact of "SET NO_BROWSETABLE ON"?

10. Re(2): "select having" problem

11. Re(4): "select having" problem

12. "set nocount on" having no effect

13. "select having" problem