When I try that modified for my tables that fit this hypothetical, I get:
CREATE TABLE `sales_table` (
`item_s` varchar(100) default '',
`price_s` varchar(100) default ''
) TYPE=MyISAM
CREATE TABLE `lookup_table` (
`item_l` varchar(100) default '',
`price_l` varchar(100) default ''
) TYP
I've tested this on a table of mine with different names, so it should work when you
tweak your columns/table. The "having clause" is a seldom taught, but highly useful
clause.
select count(1), first_name, last_name
from myuserstable
group by first_name, last_name
having count(1) > 1;
You sho
Ok, so I've broken down your problem into small, manageable steps.
First, users are provided with a box to enter a value (e.g. pumpkin) and the 1)ability
to select a ranking for pumpkin, or 2)the ability to select which old value (apefruit)
the new value-pumpkin-belongs above/below (scenarios 1
Serge,
What are you used to in the database that you are migrating from?
My guess on what would be nice is something like the ORACLE to_date and to_char
functions, which work in query strings and load data statements:
http://www.llcsystems.com/FAQ/oracle_SQL/oracle_SQL_11.htm
Though if some
If you create the tables beforehand in MySQL and then export the data into the already
created table, that should allow you finer control of your data types. To save time
you could export the table from Access, then truncate it to clear out the data, and
then change the data types as necessary
