At 09:25 AM 10/19/2004 -0400, Ed Stoner wrote:
I want to use bare numbers because that is how the users (students in this
case) are identified on the network and in the student information
system. They've been identified this way for over 20 years, so it would
be near impossible to change at th
Thanks. This worked. This is exactly what I was looking for.
Stephan Szabo wrote:
On Tue, 12 Oct 2004, Ed Stoner wrote:
I am unable to use the "CREATE USER" command with numeric user names
(i.e. CREATE USER 35236 WITH PASSWORD '1234';). Is this a limitation or
a problem somewhere with how I hav
I want to use bare numbers because that is how the users (students in
this case) are identified on the network and in the student information
system. They've been identified this way for over 20 years, so it would
be near impossible to change at this point (although it is not always
very conve
Neil Conway <[EMAIL PROTECTED]> writes:
> I don't know of an easy workaround. Why do you need numeric usernames?
There's always double-quoted identifiers:
create user "12345" with password ...
Considering that the SQL standard defines
as an , I'm not sure why Ed is expecting that he shou
On Tue, 12 Oct 2004, Ed Stoner wrote:
> I am unable to use the "CREATE USER" command with numeric user names
> (i.e. CREATE USER 35236 WITH PASSWORD '1234';). Is this a limitation or
> a problem somewhere with how I have things configured? Is there are
> workaround?
I believe you can create a
On Wed, 2004-10-13 at 06:31, Ed Stoner wrote:
> I am unable to use the "CREATE USER" command with numeric user names
> (i.e. CREATE USER 35236 WITH PASSWORD '1234';). Is this a limitation or
> a problem somewhere with how I have things configured? Is there are
> workaround?
A username is an i
I am unable to use the "CREATE USER" command with numeric user names
(i.e. CREATE USER 35236 WITH PASSWORD '1234';). Is this a limitation or
a problem somewhere with how I have things configured? Is there are
workaround?
Any help would be greatly appreciated.
--
Ed
