Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
There are many ways to represent data using binary like - unsigned, signed magnitude, 1s/2s complement, offset-M,
floating-point, ASCII, and Unicode. Why do we need so many different ways?
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I am given to know that video blobs should not be stored in MySQL. But what if the video is very small with a maximum length of 5 seconds. Is it okay to store small videos(less than 5 seconds) as blobs in mysql?
It's okay to store media data as a BLOB, regardless of length, as long as the content isn't larger than the maximum size for the data type (64KB for BLOB, 16MB for MEDIUMBLOB, 4GB for LONGBLOB).
Many software developers will insist that media belongs in files, not in the database, but there are good reasons to store data in a database too.
This is basically a matter of opinion. The best solution for your project may be different from their project.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Is there a standard for varchar length relating to storing company/business names?
I have looked everywhere and cannot find an answer.
If not, what would be an ideal length to cover the majority of scenarios?
I'm going to go out on a limb here:
No
There is not in general, though there are some guidelines for some of these kinds of fields, for some organisations, in some countries (see answers to List of standard lengths for database fields).
You'll have to use best judgement. Quick google search the longest I could find was a little over 100 characters - if you're not stuck for space, throw in a few hundred to be safe, otherwise why are you strapped for space? Pull it out into a lookup table, then make the column in that table wide and move on; angsting over this will not earn you anything.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am trying to decide on what will be more efficient between two different systems for MySQL to handle my data. I can either,
1: Create around 200 tables, each having around 30 rows & 5 columns.
2: Create 1 table, having around 6000 rows & 5 columns.
I am using Laravel for this project and Eloquent will be handling this. Does anybody have any opinions on this matter? I appreciate any/all responses.
Option 2.
For such low row counts the overhead both in terms of programming effort and computation of joining 200(!) tables far outweighs the "flat file" approach. Additionally, MySQL will attempt to cache the entire 6000-row table in RAM, assuming you're not storing massive BLOBs.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Which of these query would be faster?
1) Complicated query with subqueries
2) Simple query without subqueries but leave the extra processing work to application
I am deciding on which approach to take. I do not have real code to test against at the moment. Can those with more experience provide the answer?
It depends on the rows in the table and the sub queries you are using. Check the manual for query optimizing.
visit http://dev.mysql.com/doc/refman/5.0/en/optimization.html
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I know my question sounds stupid but I'm curious why almost all programming languages I know uses true/false or 1/0 for boolean types.
Yes/no is meaningful than 1/0 and is shorter than true/false. Is there any logical reason why true/false is preferred?
Note that I'm not trying to convince everybody that yes/no is more appropriate, I am just curious why.
"Yes" and "no" are ambiguous. Different languages treat them differently, especially when used multiply such as a double negative. The other options lack this ambiguity.