Digest mode for this list is 2 digests a day.
-Original Message-
From: Paul Fine [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 3:37 PM
To: [EMAIL PROTECTED]
Subject: Digest Again, PLEASE SOMEONE HELP?
Unless I am misinformed, subscription to the DIGEST format of this list
"You need a license if you sell a product designed specifically for use
with MySQL or that requires the MySQL server to function at all."
Actually, could someone from MySQL clarify this bit for future reference?
If my application includes a standardized method of access such as ODBC, or
provides t
Richard,
If you want to protect against hard drive failures then a RAID setup is
probably the best option. A RAID will ensure that you always have an
up-to-the-instant backup of all of your data in case a drive goes bad;
however, a RAID won'tstop a bug, virus, or error from screwing up you
It is a good idea to stick with the MySQL branch that you currently use in
production. The only reasons I can see to do otherwise are 1) if you need a
feature introduced in one of the newer development trees or 2) if your
project is in its early stages and you want to avoid the hassle of upgrading
If you are using *nix, fire up the mysql command-line client and type the
following:
\P more
Then hit enter. That forces the client to pass all of its output through
the more command and will thus return a screen's worth of records at a time.
\P will pipe the client's output through whatever you
Steve,
There is really no point in creating a separate table or group of tables for
each user. Your concern seems to be that you will make a typo and the user will have
the wrong supplier_id--well, you can make typos that send data to the wrong table just
as easily. Peter's suggestion
Steven,
I'm currently running a LAMP setup much like the one you described. A
plain text username and password is really the best way to go for giviing
PHP what it needs to access MySQL. There are other options, but they are a
lot of work to implement and in my opinion not worth the extra
Chris,
What version of MySQL are you using and what table type (InnoDB, MyISAM,
etc.)? I followed your procedure and was unable to replicate the problem
with MySQL 4.0.14 on a MyISAM table.
-Rob
-Original Message-
From: Chris Edwards [mailto:[EMAIL PROTECTED]
Sent: Wednesday, Aug
Andreas,
I don't know of a standard for naming such things. My advice is to group
your table names with a prefix if they are related to one another. Name
fields in such a way that the field's *purpose* is clear to you;
e.g.-"checked_out_by", "checked_out_date", "is_checked_out", etc. Mak
Karam,
If you look closely you'll see that it is not using the index in either of
your examples. Each query claims to scan all 33914 rows in the table, which
seems like the correct behavior. MySQL does not have an index built on the
substrings, so it has to generate each substring before
Cory,
I'm not sure I understand what you're asking. MySQL casts the data to the
appropriate column type when that data is entered into the database. Data
in a varchar column is always stored as a string, just as data in an INT
field is always going to be of type INT.
-Rob
-Original
Prabu,
This is kind of off-topic, as it is a PHP problem. ;) Those error
messages are telling you that the variables you are trying to use were never
initialized. This suggests to me that your PHP installation is set up with
the register_globals option turned off. This means all of your
Aric,
Are you running the linux version of your database on a shared web host?
Some web hosts prevent you from using % as a host identifier for security
reasons. I would also check to see if the permissions were defined at the
proper level (in other words, have you set up access prvis for
For the following I am assuming you didn't edit that output for security
reasons. What I see immediately wrong is that you are not passing a
username to mysql (If you were, then there would be something like
'[EMAIL PROTECTED]' there). Of course you can set MySQL up so that it does
not require a
Hi Charla,
Generally if the tables will be related to each other then you want to keep
them in the same database. as an example, you would want to link quiz
scores to the individual students registered in your class. It is a little
easier to do table joins and such when there is only one
I have a copy of 3.23.56 running on one of my machines and it does NOT wrap
auto_increment columns when the upper limit is reached. I haven't tested it
with any newer versions, though I doubt they'd be any different. If this is
a concern for you then I would suggest using a bigger column type for
I'm actually working on a large Filemaker to MySQL conversion project right
now. I don't need live data at this stage, so I've got a script running
that reads in a FilePro-generated CSV file each night. It works fine,
though early on we had a problem with our old version of Filepro not
exporting
17 matches
Mail list logo
