Forum Replies Created
-
AuthorPosts
-
seanhoggeMember
Dump file (second attempt)
seanhoggeMemberDump file as requested (posted below)
seanhoggeMemberIs there any update on this issue? It’s still occuring, and it’s unpleasant to have paid for software that has a basic function that doesn’t work.
seanhoggeMemberI will be buying a license soon! I've just started a company, so we're getting accounting squared away.
I've discovered that it was not my data entry that was the issue.
I was using a System DSN (Win2k3) through the ColdFusion Administrator (CFAdmin). When I switched the data source driver to a pre-configured “MySQL 3.x” driver, the data came back flawlessly with DATETIME and TIME types!
seanhoggeMemberThat's quite understandable. As I've said, this discussion doesn't even really belong here.
I must say that you and Ritesh are some of the more helpful and knowledgable around. I hope you take my wasting your time as a compliment.
I just typed it into SQLyog first. Then I entered in through the command line. Same results. With 20:00:00 I get a null value or empty string, with 00:08:25, I get the dates.
Obviously, something is up with my data format. I know this is tedious at this point. Don't worry further about it. Once I figure it out, I'll let you guys know just for the hell of it. Thanks for the assistance!
seanhoggeMemberYou may be absolutely right Mr. Laursen.
I put in the value “00:08:25” for instance.
Coldfusion returns (JDBC DSN): {ts '1970-01-01 00:00:00'}
ASP (ODBC DSN): 7/28/2005
Obviously I am not understanding the TIME type. I was under the impression that it was HH:MM:SS.fraction. Why would Coldfusion think it a DATETIME and why would VBScript think it a date?
I feel like I'm being obtuse here, so if it's something stupid and obvious, don't hesitate to say so with as much mockery as you feel necessary.
seanhoggeMemberThe data type was not a TIMESTAMP. It was a TIME type.
The data was hand entered by me (dummy data for testing during development). Everything appeared to have non-null values in SQLYog, and I am positive (barring hallucinatory optimism) they were formatted correctly.
When I ran an identical query (ColdFusion has a nifty feature that shows the SQL string sent to the database after all processing) by cutting and pasting into SQLyog, the data was returned without a hitch.
I'm feel it's a ColdFusion issue from what I've seen. Which makes this thread somewhat inappropriate here.
I will look through the Google results you showed me, though I've been through most of them. The new ones might have some leads. If I find anything definitive I will report it here anyway.
Coincidentally, I simply separated the DATETIME into a DATE field and a VARCHAR field for the time. I can control the user input, so that'll have to work for now. All the Date functions and comparisons work now.
Thanks for your help, I'm not as puzzled as to what caused this, and I think a little more work will yield an answer.
seanhoggeMemberDoesn't it throw an error giving you a line number when you attempt to import the text file to the webserver?
seanhoggeMemberAs far as adding tables, I just right click on the database drilldown on the left side, and select “Create Table…”
To edit a table, left click it in the drilldown on left side, then press F6.
As far as why you can't add data, I see no reason you can't add data simply by entering it into each field, then hitting the save changes button. Can you give more information about the database and table type? Perhaps someone else knows more about what might cause this issue than I do, though.
seanhoggeMemberI've been limited on database choices since I began doing this stuff. I'm only now coming into my own hardware and software choices, so these minor details are excellent to debate.
seanhoggeMemberI see now. I didn't think he was saying that a TINYINT(1) is precisely the same as BOOL, only that their function was similar. It was early in the morning, maybe it was pre-coffee.
seanhoggeMemberFrom what you posted, I was able to create an .sql file and a test database. This is what I put in the text file:
USE testing;
drop table if exists testing.testtable;
CREATE TABLE testtable (
col1 varchar(6) default NULL,
col2 varchar(20) default NULL,
col3 varchar(20) default NULL,
col4 char(2) default NULL,
col5 varchar(20) default NULL
) TYPE=MyISAM;
USE testing;
insert into testtable values ('57622','Cherry Creek','Ziebach','SD','South Dakota'),('57623','Dupree','Ziebach','SD','South Dakota');
It worked without a hitch on SQLyog v4.05 as long as the testing database exists. When I tried to run it a second time (meaning the table already exists) I again received no errors. I can't see what might cause the error unless you're leaving those ticks or apostrophes in your text file somewhere.
Sorry if that doesn't help you at all.
seanhoggeMemberI think Ritesh was correct as far as MySQL's changing of BOOL to TINYINT(1) based on the following link:
http://dev.mysql.com/doc/mysql/en/other-ve…lumn-types.html
I agree that is is definitely not the same data type in a classical sense, though. As long as it's easy to store what is essentially a 1 or 0 (true/false) value it suits my purposes. I suppose it might cause conflicts in code that doesn't use stored procedures (such as they are in MySQL 5).
seanhoggeMemberAlright. That's embarrassing. I just assumed – well, you know the rest.
Thanks for replying so quickly. Good morning!
seanhoggeMemberI did a search, and only found two posts regarding this problem, so forgive me if this is not the best place to mention this.
I'm using v4.05, and I am adding a column to a table. For the life of me I cannot make it add a bool type column. It converts it to a tinyint(1). Is there something I'm missing? I wouldn't put it past me to be doing something obviously wrong (it's late, I've been working for a while).
Thanks for your assistance and for what is, overall, a brilliant product.
-
AuthorPosts