Category: "Programming"
A careless mistake in ActiveRecord for MySql
I am writing a program for myself by using ActiveRecord. I am an MS SQL Server Develper. So, I just did in a careless mistake. I called a table , User. If you call a table will crash with system table name, we use '[' and ']'. I hardcoded the table name in '[User]' in a Model class for ActiveRecord. I can't create a schema by Active Record. Because in MySql, we use '`'. So, it should be
Code
[ActiveRecord("`User`")] | |
| |
public class User : ActiveRecordBase |
Not
Code
[ActiveRecord("[User]")] | |
| |
public class User : ActiveRecordBase |
Windows Mobile without Visual Studio
http://www.codeproject.com/KB/mobile/WiMoSansVS.aspx
That is a good article to teach yourself for the mobile application in SharpDevelopment
WPF Programmer is easy to Android Programming
I am learning the application programming on Android OS. I found that is easier to catch up because I am a WPF Programmer. Both of them are using xml to draw UI. That is not a strange thing for myself.
Use tryparse if that is possible or have a validation
I faced a number of error for parsing a string into int. In most of cases, there is a validation missing.
Code
If (IsNumeric(str)) | |
{ | |
int i =0; | |
Int32.TryParse(str,out i); | |
} |
You can use regex inside IsNumber or use foreach loop to check whether each character is numberic.
BUT NEVER NEVER DO LIKE THIS:
Code
try | |
{ | |
int i= Int32.Parse(i); | |
} | |
catch(FormatException) | |
{ | |
// Error Hanlding | |
} |
Try-catch is an expensive operation!!!!!!!!
Secondly, I like to use TryParse even in the case, the progam can tolrate invalid value. TryParse can allow the logic to continue execution. I hate some things like stack track on the screen.
Server Side logic vs Client Side logic
I think Server Side and Client Side, both have advantages and disadvantages.
Server Side:
Adv:
- More efficiency
- Easy to scale up(if the process is too complex, we can use load balancing)
Dis:
- Hard to deploy, to some complex operations, it may be required CLI store procs.
- More expertises required
Client Side:
Adv:
- Easy to be implement, You need to know C#
- Easy to deploy
- Easy to be manage
Dis:
- Less efficiency
I think, in generally, for complex operations, we can try to put that into the server side. For simple operations, just putting them into the client side logic. That is simple.