newbie mysql-SQL question

Thank you in advance for your help. I'm trying to run two tables with identical table structures into a single continuous resultset. To simpify, I have one table with columns ID int and NAME varchar(32) and another table2 with columsn ID int and NAME varchar(32), and each table has 100 items.

any way to do this with SQL ???

Thank you in advance for your help. I have a table which has a timestamp column. Now, I want to add a column of type datetime and transfer the original timestamp (date or original insertion) into the new datetime column (so as to preserve this information for all posterity in case an new update

Re: mysql.org

Again, Mr. Johnston, NuSphere shows very poor public relations abilities. Adopting such a condescending tone toward MySQL AB, to which, Sir, you must understand, you are completely indebted for everything that you have and are, will further alienate you from the supporters of MySQL. NuSphere's

SQL executes on command-line but not in PERL

Hi, everyone, I've recently run into a strange phenomenon. I try to tun the statement "update accounts set loggedin=10 where username='user'" -- works fine from the command line. But I used it in a PERL DBI situation and it does NOTHING -- no error, nothing. I know the PERL code is fine,

Re: SQL executes on command-line but not in PERL

Thank you, Ryan, but the PERL code runs perfectly if I try it on any other field. It just doesn't run on THIS field. It's not a SPECIAL field in any way (like PRI Key or Unique or anything like that). When I run it in a compound statement like "update accounts set users=10, loggedin=10 where

Windows ME / 2000 VB problem with BIGINT data type

I wrote to the list earlier on the above problem. I had a VB app that accessed a mysql (on Linux) table through MyODBC. Apparently the problem is that the new ODBC connection providers in Windows ME / 2000 do not like the BIGINT datatype. Yet, strangely, MS Access 97 can import the data

Re: Windows ME / 2000 VB problem with BIGINT data type

fit into the INT size type. I think I was a bit ambition in first defining the tables. Thank you, Laszlo Szijarto - Original Message - From: "Laszlo G. Szijarto" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 17, 2001 2:22 PM Subject: Windows ME / 2000 VB

Winblows ME and MYODBC

Sorry, folks, if these seems off topic. I know it's a Winblows problem rather than MYODBC. After having "upgraded" to Windows ME from Windows 98, and am unable to run a query (select * from table -- in Visual BASIC) on only one table in my databases. I get a runtime error that the Microsoft