From: kennedy-downwithspammersfamily@attbi.net   
      
   "JP Belanger"  wrote in message   
   news:b399d6ce.0408170627.12849129@posting.google.com...   
   > afilonov@yahoo.com (Alex Filonov) wrote in message   
   news:<336da121.0408161150.2c0d78d9@posting.google.com>...   
   > >   
   > >   
   > > If you are trying to restrict number of rows to <= 50, there is   
   something   
   > > wrong with database design. It'll help if you post what you are trying   
   > > to achieve (in simple words)...   
   >   
   > Are you saying I was unclear ? :)   
   >   
   > I keep track of sessions in a database.  Exceeding a fixed number of   
   > sessions should not be allowed.   
   >   
   > The reason I do not keep the cound in the Java application was that I   
   > wanted to keep the application stateless, to allow for simple load   
   > balancing.  I thought the database could help me, but at the same   
   > time, I think helping me, the database would sacrifice a lot of   
   > performance.   
   Why not just set the parameter in the init.ora file that restricts the   
   number of logons.   
   Very simple and reliable.   
   Jim   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)