SQL Calling Methods

I am doing some grouping in SQL with the grouping determined by a
method call (because the grouping is user-defined and quite
arbitrary). So far, so good. Are there any pitfalls that I need to
watch for?

I do not need to do this, but is it still dangerous to move a
table pointer even if one restores it?

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

SQL statements should not move the record pointer of the queried tables.

But if you do move a record pointer then move it back, it shouldn't change
anything - EXCEPT if there's row buffering on the table and a field has
changed. In that case, the changes will be automatically saved.

It's rare to run a query on a buffered table, but if you do, make sure you
understand WITH BUFFERING.




"Gene Wirchenko" wrote in message
news:2gpl545cscpgqj2q3la39bo8c9us58gh89-at-4ax.com...
> I am doing some grouping in SQL with the grouping determined by a
> method call (because the grouping is user-defined and quite
> arbitrary). So far, so good. Are there any pitfalls that I need to
> watch for?
>
> I do not need to do this, but is it still dangerous to move a
> table pointer even if one restores it?
>
> Sincerely,
>
> Gene Wirchenko
>
> Computerese Irregular Verb Conjugation:
> I have preferences.
> You have biases.
> He/She has prejudices.