fenway
-
Posts
16,168 -
Joined
-
Last visited
-
Days Won
4
Everything posted by fenway
-
Of course -- I just mean to say that there's nothing wrong with tying a MySQL DB to a NoSQL document image store -- pick the right hammer for each nail.
-
I'm not sure where your question lies -- in the DB queries,, the PHP syntax for loops, or the HTML rendering?
-
This is a common misunderstanding -- if you have a bowl of fruit, and you ask someone to hand you apples and oranges, you'll likely get 2 kinds of fruit. But this isn't a Boolean AND -- it's a Boolean OR. Asking for the fruit that is both an apple AND and orange will result in no matching fruit.
-
That's not how a forum works -- share your advice with everyone.
-
Obviously, adjust to suit your column needs accordingly (untested): SELECT * FROM files INNER JOIN platforms ON ( files.id = platforms .file_id ) INNER JOIN resolutions ON ( files.id = resolutions.file_id ) WHERE resolutions.resolution = '$match_resolution' AND platforms.platform ='$match_platform';
-
To be clear, it's a bad idea to store images (file contents) in an RDBMS -- noSQL is great for this stuff (because your files are still accessible from multiple nodes, etc.).
-
What makes you think you're getting table locks?
-
Requirement? Whose?
-
That's how date strings are sorted, too (i.e. outside of mysql).
-
The comparison operator will always "work" -- but the implicit casting just might not do what you'd expect.
-
I suppose you can do it that way, though I never have -- what happens in PHP if the $id's aren't contigious? Will you get a sparsely populated array?
-
If you're talking about InnoDB tables, it's very rare to get a table lock during normal CRUD operations -- unless you somehow issue a write statement that can't use an index.
-
Writing out N forms isn't great either -- what if they want to make multiple changes? Usually, you just need another field with the ID, and then append this ID to each field name.
-
MySQL doesn't know about clicks -- what are you actually trying to achieve?
-
Without a query, EXPLAIN is meaningless.
-
What we didn't "trust" was your explanation -- as you indicated, that's the hardest part to communicate.
-
Returning the Correct ID with column groups and...
fenway replied to AnalyzeThis's topic in MySQL Help
First, make the query without joining back to the contact name table. -
I simply meant that if you executed the statement, if would be plainly obvious from the syntax errors where the problems are.
-
And TIMESTAMPs have time zone fun built-in.
-
You know that SQL can tell you if your statement parses correctly -- and we can't guess -- but I can tell you that without quoting, you're going to in trouble. That's what placeholders are for.
-
You can use COALESCE(), too.
-
Please don't mark topics solved without posting solutions.
-
Use "SHOW OPEN TABLES" within the session.
-
You're new here -- please share how you "figured it out" next time -- even if it only took 3 minutes for you, others may benefit from your post. The issue here was quoting the column names.
-
If you post your entire code one more time, I'm going to lock this thread for good -- just post the relevant code snippet, nothing more. If you feel the urge to include the entire script, use an attachment.