really up to date?
Submitter-Id: submitter ID
Originator:Gordon Burditt
Organization:
MySQL support: none [none | licence | email support | extended email support ]
Synopsis: mysql_fix_privilege_tables doesn't fix the privilege tables
Severity: non-critical
Priority: low
I know this is an old query, but still, problems . . .
I've tried these both, but something is amiss - probably my interpretation.
Every time I try to use LAST_INSERT_ID() I get a complaint that the
query has a problem.
E.G., $qry=$qry.;select LAST_INSERT_ID(); will blow up on me every
time
So, one of my associates has made a linking table (some people also call it
intersection table, cross tab table, but i believe that the propper way to
model a many to many relationship is via a linking table). in the linking
table, there is no primary key defined.
Let us suppose you wish to
I Have a question relating to setting up users for our customers on a shared
server environment. I can not find this answer in the documentation so I am
trying here.
Is it standard practice to give the user of the database (site owner) one
set of permissions which I figure should be:
select,
The tables will be used to enable users to enter comments concerning what
they believe happens at individual conjunctions. For example, in astrology,
let's say one enters a comment of what happens when the Moon enters
Scorpio. These comments can then be called by other users and rated with an
Does anybody know if there is a function to retrieve the next unique ID
number for a record to be made in the future?
I believe you can reliably allocate sequence numbers from a sequence
table (a table used only to dole out sequence numbers) like this:
create table sequence ( seq int not null
I would like to send multiple SQL statements using the C
API mysql_query. I have a large string with 20 SQL statements. When
I call mysql_query with that string, only the first one is processed.
Is there a way to do what I'm doing without separating the statements
into individual calls
I did not mean for this to be an off-topic PHP post, what I was noodling
about here was a mySQL means to provide a more secure access for
scripting languages like Perl, Python and PHP - which end up with
insecure username and password config files all over the Internet.
There's a problem here:
