In the last episode (Sep 18), Victor Subervi said:
> Can someone please explain to me why Passengers.weight comes up null for
> the last value sometimes, and other times it comes up with the value 155??
Passengers id 1 through 3 have a weight of NULL in the Passengers table, and
passenger 4 has a
I have the following pseudo code running on mysql 4.x:
set @cnt:=0;
insert ignore into dest_table
select t1.field1, t1.field2, t1.field3, t2.field1,
t1.field3, t2.ts, @cnt:=...@cnt+1
from table1 as t1 left join table2 as t2 using (field1, field2)
order by t2.ts;
This works pe
I want to transfer a database(not MySQL) to MySQL(only the tables,not stored
procedures,views etc.).Using SQLWays I gotseveral problems(It needs some
expertise).Now using SQLMaestro DataWizard I exported some tables to csv format
forimporting with mysqlimport,I previously created the database w
Hi;
Can someone please explain to me why Passengers.weight comes up null for the
last value sometimes, and other times it comes up with the value 155??
mysql> select p.id, c.id, p.name, p.weight, m.amount, p.round_trip,
c.first_name, c.middle_name, c.last_name, c.suffix, c.sex, p.confirmation,
m.t
Mon,
If I understood well, skip-locking isn't for you. IMHO, if you have a
unique process (mysqld) that manages your tables and statements are
causing deadlock, maybe you should try InnoDB. Try simulate a parallel
environment changing the storage engine and tell us. (Take a look in
the modifier 'L
Keep in mind that to store a number as a 32 bit unsigned integer takes
4 bytes of data no matter how small or large that number is as long as
it is less than 4,294,267,296. If you store numbers as a string like it
is in your file it takes 8 bits per digit so for 19,999,999 it would
take 8 byt
