I have my first Drobo -.6TB of disk. With Drobo and Crash Plan I think all my files are safe and sound. It will take a while to move my files and I wish the Drobo server could run more apps but that is not a priority at the moment.
I made my first github project. dbKnow
I have not upgraded my jsRender in a while because it works fine. I’m about to get back on the latest version.
45% Of Greeks Have Never Used The Internet or Greece just has an older population or the Internet is more expensive in Greece.
Am I the only one who reads this and thinks that all the Windows Phone 7 apps wont work.
Firstly read this.
1. Adding a prefix is a much better idea. Using a schema is fine also. A prefix will separate transaction tables from lookup/static data table. Grouping tables that work together is a better practice.
2.I’m 50/50 on this. Tables have many records, a plural wont hurt.
4.Unnecessary prefix should be avoided but necessary and useful ones should be kept,
5. There is more to it than this. Use Google and get some good advice.
6. Use bigInts please.
7. Um no. That wont happen. A big int is 8 bytes and your varChar can be smaller.
8. No question ever has a yes/no answer ever. You will always want a third choice so choose an int now and save time latter. Using an int means all choice fields are of the same type, not matter how many choices.
9. OK. We have a winner
10. This better performance is a myth but generally a good idea.
11. This does not belong in the list
12. Actually do this for the highly used tables to spread out IO.
13. Do this for all databases unless you have one you can lose.
14. If you add a constraint you will need an index.
15 or use dbknow.com (coming soon)
16. Google this, there is a lot more to it, choosing the order of fields in the index is crucial
17. Or save money if you do not need it.
18. The database will do this for you. Never mind carry on
19. Huh. This is not helpful or correct.
If Microsoft wants to sell tablets and phones it needs apps. What it needs even more is the internet, unless the browser on their tablets and phones is compatible with webkit and better it wont run the sites people need and then it will suck and then no one will buy it and then no one will write apps.
If you put an illustration like this in a book you are smoking crack. Exactly what percentage of readers do know know what a toolbar is, yet read a book called “Beginning IOS5 Development”.
I’m wondering why people develop for Windows phone 7. Is it because the browser is so bad that it wont run HTML5 apps?
Please please do not do this. This is why people hate their software. It fixes a problem in the developer’s mind not in the user’s mind.
Here is the issue at hand. Say, user pulled up an entry form and made some changes. Then the above mentioned user clicked browser back button, navigating away from the current page, and thus loosing all the pending changes. A friendly software application should warn the user, shouldn’t it?
No no no no. The user took an action, respond and obey, especially with the sacrosanct back button of all things. Nagging them is never good. What if they want both; to go back and not lose there changes.
Let’s start with a better definition of the problem: The user clicks the back button while editing and could loose changes. How should the application respond. Let’s eliminate “Pop up a dialog box”: as that is never the right answer. How about saving the state so if the user clicks the forward button to return to the page their data has not been lost. Most browsers will do this automatically and the users understand the flow.