Xojo Conferences
MBSSep2018MunichDE
XDCMay2019MiamiUSA

realdatabase, no limit? (Real Studio network user group Mailinglist archive)

Back to the thread list
Previous thread: [ANN] App Bundler 1.0b2
Next thread: RB 5.5 irregularities


Using services   -   Jan Erik Moström <
  realdatabase, no limit?   -   hector schisa
   Re: realdatabase, no limit?   -   Will Leshner
   Re: realdatabase, no limit?   -   Joseph J. Strout
   Re: realdatabase, no limit?   -   hector schisa
   Re: realdatabase, no limit?   -   Will Leshner

realdatabase, no limit?
Date: 28.02.04 16:27 (Sat, 28 Feb 2004 10:27:33 -0500)
From: hector schisa
Since the RB manual doesn't list the LIMIT modifier for the sqlselect
statement, and since it doesn't do anything when i add it to a select
statement for a Realdatabase, I assume the Realdatabase doesn't support
the LIMIT modifier. True?

if so, shouldn't it be a feature request(?) since one doesn't want to
take in to many records sometimes (either for memory or other
considerations), especially when one wants the resultant recordset to
utilize all a table's records. Or is there another simple way to go
about setting limits on what a select statement returns?

I suppose one could use an index:, but if records are sorted somehow,
the index fields would be out of order and not useful for grabbing the
next bunch of records; and if there's a condition on the search, then
using an additional condition about the index would only search within
the index parameters.

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Re: realdatabase, no limit?
Date: 28.02.04 16:54 (Sat, 28 Feb 2004 07:54:58 -0800)
From: Will Leshner

On Feb 28, 2004, at 7:27 AM, hector schisa wrote:

> Since the RB manual doesn't list the LIMIT modifier for the sqlselect
> statement, and since it doesn't do anything when i add it to a select
> statement for a Realdatabase, I assume the Realdatabase doesn't
> support the LIMIT modifier. True?
>

Hmm. Doesn't it give you a syntax error when you use LIMIT in your SQL?
If column constraints result in a syntax error, shouldn't LIMIT as
well?

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Re: realdatabase, no limit?
Date: 28.02.04 19:53 (Sat, 28 Feb 2004 12:53:43 -0600)
From: Joseph J. Strout
At 10:27 AM -0500 2/28/04, hector schisa wrote:

>Since the RB manual doesn't list the LIMIT modifier for the
>sqlselect statement, and since it doesn't do anything when i add it
>to a select statement for a Realdatabase, I assume the Realdatabase
>doesn't support the LIMIT modifier. True?

True.

>if so, shouldn't it be a feature request(?)

If someone wants it, yes.

Cheers,
- Joe

Re: realdatabase, no limit?
Date: 28.02.04 19:11 (Sat, 28 Feb 2004 13:11:12 -0500)
From: hector schisa

On Feb 28, 2004, at 11:23AM, REALbasic Network Users Group wrote:

>
>> Since the RB manual doesn't list the LIMIT modifier for the sqlselect
>> statement, and since it doesn't do anything when i add it to a select
>> statement for a Realdatabase, I assume the Realdatabase doesn't
>> support the LIMIT modifier. True?
>>
> Hmm. Doesn't it give you a syntax error when you use LIMIT in your SQL?
> If column constraints result in a syntax error, shouldn't LIMIT as
> well?

No to first question. Only tried it once, but it went right ahead and
gave me all the records (RB 5.5 OS X).
Leave the second question to RB developers.

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Re: realdatabase, no limit?
Date: 28.02.04 19:17 (Sat, 28 Feb 2004 10:17:58 -0800)
From: Will Leshner

On Feb 28, 2004, at 10:11 AM, hector schisa wrote:

> No to first question. Only tried it once, but it went right ahead
> and gave me all the records (RB 5.5 OS X).
> Leave the second question to RB developers.
>

I don't know. Maybe it is ok. In the case of column constraints, to
ignore those is to create an incorrect table in your database. Better
to signal an error. But to ignore LIMIT just gives you incorrect query
results. Still not good, but maybe not as fatal.

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>