Being new to MySQL, it took a while to grok how "security" works. Now that
I have a bit of a better understanding, a mental "revalation" is coming to
the surface of my mind: since "mysql" users are NOT unix/windows-domain
"users", is the "root" user truly needed for a functional mysql environment
I am by no means an "SQL-expert", but I'll give this a shot... :)
> -Original Message-
> From: Richard Brenner [mailto:[EMAIL PROTECTED]]
> Subject: query problem
>
> I have two tables with the following structure:
>
> Users:
> | Field| Type
> | id | int(10) unsigned
> |
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Subject: [which I usually snip as it's redundant]
Re: RE: mysql is driving me mad (3)
[however it appears it would have avoided this:]
> Your message cannot be posted because it appears to be either spam
I've got a strange problem using VB to connect to a mysql database via ODBC.
The problem isn't with connecting, but rather with one particular control --
the "datalist/combo" control. In fact, the "problem" doesn't seem to have
anything to do with databases directly, BUT I figured that there is
s
This is actually a bit of a general-database question, since I'm sure it has
the same or similar repercussions regardless of which RDBMS you use, but I'm
curious: is it possible to "safely" allow users to maintain their own
passwords to a database? [and if so, how?]
I'm sure I can do this "progr
his using what VB
calls a "dataenvironment", and that is the component that seems to have the
problem. Another "wizard" within VB is a "data view" window, and that one
seems to be able to determine the proper field sizes, but when a table
