«

Hi friends,

I'm doing some cgi programming these days, using MS Access database to store uid/pwd info from registration forms in HTML pages. I considered

SELECT from Users WHERE userid = '$uid'

to see whether the received uid (from webpage forms) is already in the database, but I guess there may be more convenient ways to do this?

Thanks for ur advice!

Regent

"Regent" <> wrote in message
news:bt2nnc$1ed8$...
> Hi friends,
>
> I'm doing some cgi programming these days, using MS Access database to
store uid/pwd info from registration forms in HTML pages. I considered
>
> SELECT from Users WHERE userid = '$uid'
>
> to see whether the received uid (from webpage forms) is already in the
database, but I guess there may be more convenient ways to do this?

What would Perl programmers know or care about SQL.

"Regent" <> wrote in message
news:bt2nnc$1ed8$...
> Hi friends,
>
> I'm doing some cgi programming these days, using MS Access database to
store uid/pwd info from registration forms in HTML pages. I considered
>
> SELECT from Users WHERE userid = '$uid'
>
> to see whether the received uid (from webpage forms) is already in the
database, but I guess there may be more convenient ways to do this?
>
> Thanks for ur advice!
>
> Regent
>
>
I use MySql, and that's the way I do it, simply checking to see if anything
is returned. I think it's fairly effective, because it doesn't require much
coding either.

------------------------
Fri, 02 Jan 2004 04:00:51 GMT £¬Nick Santos wrote:
>>
>I use MySql, and that's the way I do it, simply checking to see if anything
>is returned. I think it's fairly effective, because it doesn't require much
>coding either.
>

Thanks, and how do you check by the way?

------------------------
Regent

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2004-01-02, Tintin <> wrote:
>
> What would Perl programmers know or care about SQL.

Many Perl programmers know and care about SQL. Why any of them should
answer SQL questions in a Perl newsgroup is another question altogether.

- --keith

- --
kkeller-
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/9RWchVcNCxZ5ID8RAnKwAJ9Du/s2oR0pmeyteNxjM1AGAHJIwACeMN3/
5u39HJyjfY7wXPwmYBQyXWU=
=NMz2
-----END PGP SIGNATURE-----

In article <bt2nva$2qi0e$>,
"Tintin" <> wrote:

>What would Perl programmers know or care about SQL.

I write a lot of Perl (as well as C and other languages), and I use a
lot of SQL with it. I have also used PHP with SQL, and guess what--I
think Perl DBI is more advanced than anything PHP can offer.

It was a dark and stormy night, and Tintin managed to scribble:

>
> "Regent" <> wrote in message
> news:bt2nnc$1ed8$...
>> Hi friends,
>>
>> I'm doing some cgi programming these days, using MS Access database to
> store uid/pwd info from registration forms in HTML pages. I considered
>>
>> SELECT from Users WHERE userid = '$uid'
>>
>> to see whether the received uid (from webpage forms) is already in the
> database, but I guess there may be more convenient ways to do this?
>
> What would Perl programmers know or care about SQL.

Lots. Well I've been using SQL for 15 years, and answer a lot of SQL questions here.

The above query I would probably change to
SELECT count(*) kount from Users WHERE userid = '$uid'

then test for kount>0 (using the DBI syntax to reference kount).

gtoomey

>Lots. Well I've been using SQL for 15 years, and answer a lot of SQL questions here.
>
>The above query I would probably change to
>SELECT count(*) kount from Users WHERE userid = '$uid'
>
>then test for kount>0 (using the DBI syntax to reference kount).

>gtoomey

Thanks. The idea is to check if the uid already exists and if not INSERT the new user into the db.
Now that the SELECT is already a filter, I think this filter must be cancelled before the INSERT operation, right? How do I cancel this filter without disconnecting the db? Thanks again

------------------------
Regent

>Lots. Well I've been using SQL for 15 years, and answer a lot of SQL questions here.
>
>The above query I would probably change to
>SELECT count(*) kount from Users WHERE userid = '$uid'
>
>then test for kount>0 (using the DBI syntax to reference kount).

>gtoomey

Thanks. The idea is to check if the uid already exists and if not INSERT the new user into the db.
Now that the SELECT is already a filter, I think this filter must be cancelled before the INSERT operation, right? How do I cancel this filter without disconnecting the db? Thanks again

------------------------
Regent

It was a dark and stormy night, and Regent managed to scribble:

>>Lots. Well I've been using SQL for 15 years, and answer a lot of SQL
>>questions here.
>>
>>The above query I would probably change to
>>SELECT count(*) kount from Users WHERE userid = '$uid'
>>
>>then test for kount>0 (using the DBI syntax to reference kount).
>
>>gtoomey
>
> Thanks. The idea is to check if the uid already exists and if not INSERT
> the new user into the db. Now that the SELECT is already a filter, I think
> this filter must be cancelled before the INSERT operation, right? How do I
> cancel this filter without disconnecting the db? Thanks again
>
> ------------------------
> Regent
>

I'd just do an insert, and check the return code. If its OK, or record already present, then that's whay you want.

If you do a select followed by insert, you are adding an extra database access. This may be significant if you are dealing with lots of records.

gtoomey