1. to remove MySQL 5.0, see previous post.
2. download the MySQL 4.1.22 installer from MySQL website.
3. install mysql-standard-4.1.22...i686.pkg
4. install mysqlStartupItem.pkg
5. set up MySQL config. In command prompt type:
sudo pico /etc/my.cnf
6. paste the following 4 lines into pico:
[mysqld]
default-character-set=utf8
[client]
default-character-set=utf8
7. exit pico & save file (ctrl+x, Yes for save)
8. now we can start the MySQL server using sudo:
sudo /Library/StartupItems/MySQLCOM/MySQLCOM start
9. open up command prompt, and enter mysql by typing:
/usr/local/mysql/bin/mysql -u root
EDIT: Getting it to work with OSX's installation of PHP...
Only follow the following instructions if you are having problems with the @mysql_connect method in PHP.
1. create a info.php file that calls the phpinfo(); method
----- NOTE: my version of PHP is 5.2.8
----- scroll down to the mysql section, and look for the value for key: MYSQL_SOCKET
----- MYSQL_SOCKET = /var/mysql/mysql.sock
----- goto /var/mysql and make sure mysql.sock... if the directory is missing or file is missing, you have the same problem I did. Your mysql.sock is probably inside /private/tmp...
2. in command prompt, type the following:
sudo mkdir /var/mysql
sudo chown _mysql /var/mysql
3. (OPTIONAL) in command prompt, type the following:
cp /private/tmp/mysql.sock /var/mysql/mysql.sock
4. edit the my.cnf file again, this time make sure its whole contents are the following 6 lines:
[client]
default-character-set=utf8
socket = /var/mysql/mysql.sock
[mysqld]
default-character-set=utf8
socket = /var/mysql/mysql.sock
5. restart the apache service through System Preferences > Sharing > Web Sharing
6. restart the MySQL service by typing the following 2 lines (one at a time) into command prompt:
sudo /Library/StartupItems/MySQLCOM/MySQLCOM stop
sudo /Library/StartupItems/MySQLCOM/MySQLCOM start
At this point the mysql_connect() php method should work as expected...
MYSQL: Removing MYSQL from a mac
Do the following in the terminal:
1. sudo rm /usr/local/mysql
2. sudo rm -rf /usr/local/mysql*
3. sudo rm -rf /Library/StartupItems/MySQLCOM
4. sudo rm -rf /Library/PerformancePanes/My*
5. (Edit /etc/hostconfig) sudo vi /etc/hostconfig (Remove line MYSQLCOM=-YES)
6. sudo rm -rf /Library/Reciepts/mysql*
7. sudo rm -rf /Library/Reciepts/MySQL*
1. sudo rm /usr/local/mysql
2. sudo rm -rf /usr/local/mysql*
3. sudo rm -rf /Library/StartupItems/MySQLCOM
4. sudo rm -rf /Library/PerformancePanes/My*
5. (Edit /etc/hostconfig) sudo vi /etc/hostconfig (Remove line MYSQLCOM=-YES)
6. sudo rm -rf /Library/Reciepts/mysql*
7. sudo rm -rf /Library/Reciepts/MySQL*
SQL: MySQL + USERS + MAC
when installing mysql for the very first time, you will need to create a root password in order to enter the mysql database:
mysqladmin -u ROOT_USER_NAME -p ROOT_PASSWORD
sign into mysql using the following command:
mysql --user=ROOT_USER_NAME --password=ROOT_PASSWORD
once in, you want to first navigate to the mysql database:
use mysql;
you can now insert more users to your liking by using the following commands:
create user 'SUB_USER_NAME'@'LOCALHOST';
set that person's password by using:
set password for 'SUB_USER_NAME'@'LOCALHOST' = PASSWORD('SUB_USER_PASSWORD');
now to give all permissions for the new user...
grant all privileges on *.* to 'SUB_USER_NAME'@'LOCALHOST' IDENTIFIED BY 'SUB_USER_PASSWORD' WITH GRANT OPTION;
or if you want to just grant certain privileges (in this case, SELECT):
grant SELECT on *.* to 'SUB_USER_NAME'@'LOCALHOST' IDENTIFIED BY 'SUB_USER_PASSWORD';
if you made a mistake, you can revoke the privileges by doing this:
revoke all privileges, grant option from 'SUB_USER_NAME'@'LOCALHOST';
NOTE:
1. *.* means you are granting permission to SELECT on all databases. Alternatively you could also specify a specific database, ie. mysql.user
2. GRANT OPTION is a special command that allows the SUB_USER to grant that same permission to other users
mysqladmin -u ROOT_USER_NAME -p ROOT_PASSWORD
sign into mysql using the following command:
mysql --user=ROOT_USER_NAME --password=ROOT_PASSWORD
once in, you want to first navigate to the mysql database:
use mysql;
you can now insert more users to your liking by using the following commands:
create user 'SUB_USER_NAME'@'LOCALHOST';
set that person's password by using:
set password for 'SUB_USER_NAME'@'LOCALHOST' = PASSWORD('SUB_USER_PASSWORD');
now to give all permissions for the new user...
grant all privileges on *.* to 'SUB_USER_NAME'@'LOCALHOST' IDENTIFIED BY 'SUB_USER_PASSWORD' WITH GRANT OPTION;
or if you want to just grant certain privileges (in this case, SELECT):
grant SELECT on *.* to 'SUB_USER_NAME'@'LOCALHOST' IDENTIFIED BY 'SUB_USER_PASSWORD';
if you made a mistake, you can revoke the privileges by doing this:
revoke all privileges, grant option from 'SUB_USER_NAME'@'LOCALHOST';
NOTE:
1. *.* means you are granting permission to SELECT on all databases. Alternatively you could also specify a specific database, ie. mysql.user
2. GRANT OPTION is a special command that allows the SUB_USER to grant that same permission to other users
IPHONE: NSXMLParser leak NSPlaceholderString
This is probably the most annoying leak I've every faced. With the NSXMLParser, I was getting these crazy 16 byte NSCFString leaks. The leaks traced back to [NSXMLParser parse], caused by NSPlaceholderString initWithBytes/initWithString.
I believe this is caused by the [parser:foundcharacters] method. Generally, the xml document being parsed has a bunch of \t and \n characters. It would appear these are the culprit. I got rid of the parse leaks by doing the following:
- (void)parser:(NSXMLParser*)parser foundCharacters:(NSString*)cdata {
NSString* tmp = [cdata stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]];
if(curr && tmp && [tmp length] > 0) {
curr.content:tmp;
}
}
Where curr is the variable saving the cdata 'found characters'.
I believe this is caused by the [parser:foundcharacters] method. Generally, the xml document being parsed has a bunch of \t and \n characters. It would appear these are the culprit. I got rid of the parse leaks by doing the following:
- (void)parser:(NSXMLParser*)parser foundCharacters:(NSString*)cdata {
NSString* tmp = [cdata stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]];
if(curr && tmp && [tmp length] > 0) {
curr.content:tmp;
}
}
Where curr is the variable saving the cdata 'found characters'.
Eclipse: Eclipse bin and .svn directories
Eclipse tends to like picking up .svn folders and throwing them into the /bin directory. For me, this defeats the purpose of doing a svn-ignore on the /bin directory. To prevent this from happening:
Configure Build Path > Source tab, under each SOURCE (or resource) directory, set the following excludes:
.svn
**/.svn/**
Clean & rebuild
XP: Map local directory as a drive
type in command prompt:
subst:
example:
subst e: c:\mpowerplayer\hdd
you should now see a e:\ volume in windows explorer.
subst
example:
subst e: c:\mpowerplayer\hdd
you should now see a e:\ volume in windows explorer.
UNIX: Find command
Common uses for the FIND command.
1. find all hidden .svn folders and delete them
find /path/to/search -name '.svn' -type d -exec rm -rf '{}' \;
2. find all hidden .svn folders and print them
find /path/to/search -name '.svn' -type d -print
1. find all hidden .svn folders and delete them
find /path/to/search -name '.svn' -type d -exec rm -rf '{}' \;
2. find all hidden .svn folders and print them
find /path/to/search -name '.svn' -type d -print
SVN: Subversion Server + MAC
This tutorial assumes that you have already installed the SVN binaries, and modified your PATH to the svn/bin.
Step 1: Creating a local repo
svnadmin create /path/to/repo
Step 2: Change the default configurations, svnserve.conf
[general]
anon-access = none
auth-access = write
authz-db = authz
password-db = passwd
realm = Subversion Server
Step 3: Edit the authz file
[groups]
admin = alex, bob, cathy
engineers = donny, emily
producers = frank
visitors = greg
[/]
* =
@admin = rw
@engineers = rw
@producers = rw
@visitors = r
Step 4: Edit the passwd file
[users]
alex = pw1
bob = pw2
cathy = pw3 (... and so forth)
Step 5: Chmod the entire repo directory
cd /path/to
find repo -exec chmod 777 '{}' \;
Step 6: Start the svn server
svnserve -d -r /path/to/repo
Step 7: Do a sample checkout
svn co svn://localhost /download/path --username bob --password pw2
Hopefully it works :) Oh yea, and to restart the server, you can use the command killall svnserve
Step 1: Creating a local repo
svnadmin create /path/to/repo
Step 2: Change the default configurations, svnserve.conf
[general]
anon-access = none
auth-access = write
authz-db = authz
password-db = passwd
realm = Subversion Server
Step 3: Edit the authz file
[groups]
admin = alex, bob, cathy
engineers = donny, emily
producers = frank
visitors = greg
[/]
* =
@admin = rw
@engineers = rw
@producers = rw
@visitors = r
Step 4: Edit the passwd file
[users]
alex = pw1
bob = pw2
cathy = pw3 (... and so forth)
Step 5: Chmod the entire repo directory
cd /path/to
find repo -exec chmod 777 '{}' \;
Step 6: Start the svn server
svnserve -d -r /path/to/repo
Step 7: Do a sample checkout
svn co svn://localhost /download/path --username bob --password pw2
Hopefully it works :) Oh yea, and to restart the server, you can use the command killall svnserve
MySQL on OS X
Download MySQL at: http://dev.mysql.com/downloads/ (More Specific) & install the DMG
1. Open up Terminal
2. Add /usr/local/mysql/bin to PATH
- cd ~
- emacs .profile
- export PATH="$PATH:/usr/local/mysql/bin"
3. Restart Terminal
4. Create new user for login
- mysqladmin -u USERNAME -p -password PASSWORD
5. Log in to MySQL with new user created
- mysql --user=USERNAME --password=PASSWORD
You should be in MySQL now
1. Open up Terminal
2. Add /usr/local/mysql/bin to PATH
- cd ~
- emacs .profile
- export PATH="$PATH:/usr/local/mysql/bin"
3. Restart Terminal
4. Create new user for login
- mysqladmin -u USERNAME -p -password PASSWORD
5. Log in to MySQL with new user created
- mysql --user=USERNAME --password=PASSWORD
You should be in MySQL now
SERVER: FSB vs. RAM
Taken from: http://www.directron.com/fsbguide.html
Front Side Bus (FSB) - The Front Side Bus is the most important bus to consider when you are talking about the performance of a computer. The FSB connects the processor (CPU) in your computer to the system memory. The faster the FSB is, the faster you can get data to your processor.
System clock - The actual speed of your FSB with out any enhancements (such as double pumping, or quad pumping) on it. An often-misunderstood property of the system clock is its effect on processor speed. You see, a thing called a "CPU Multiplier" determines the speed of a processor in MHz. If you take the CPU Multiplier and multiply it by the System Clock speed you get the speed of your processor.
DDR2 - DDR2 memory has a different approach to design at the chip level than DDR. The simplest way to understand how it works would be to think that at the low level it had two chips of half the stated memory speed working in tandem together to achieve the full speed stated. So for DDR2 400 it would be something like 2 chips of DDR200 working together to achieve the full 400 speed. Notice that I say "chips" not sticks of memory. All this happens on 1 stick of memory. In other words, when calculating in tandem in respect to the FSB, just divide the given speed by 2.
Example:
Assume my quad-core, quad-pumped FSB = 1066MHz.
This means my System Clock is 1066/4 = 266MHz.
My CPU is clocked at 1.6GHz = 266MHz * CPU MULTIPLIER.
This means my CPU MULTIPLIER must be 1600/266 = 6.
Now here are my options for DDR2:
(A) 533MHz/2 = 266MHz. This is an EXACT MATCH to my System Clock.
(B) 667MHz/2 = 333MHz. This is the next highest speed available.
(C) 800MHz/2 = 400MHz. This is pure overkill since the System Clock is capped at 266MHz.
In these stated cases, (B) is actually preferred. (A) is an exact match which means sometimes its lag can adversely affect the CPU bus speed. As stated, option (C) is overkill.
Front Side Bus (FSB) - The Front Side Bus is the most important bus to consider when you are talking about the performance of a computer. The FSB connects the processor (CPU) in your computer to the system memory. The faster the FSB is, the faster you can get data to your processor.
System clock - The actual speed of your FSB with out any enhancements (such as double pumping, or quad pumping) on it. An often-misunderstood property of the system clock is its effect on processor speed. You see, a thing called a "CPU Multiplier" determines the speed of a processor in MHz. If you take the CPU Multiplier and multiply it by the System Clock speed you get the speed of your processor.
DDR2 - DDR2 memory has a different approach to design at the chip level than DDR. The simplest way to understand how it works would be to think that at the low level it had two chips of half the stated memory speed working in tandem together to achieve the full speed stated. So for DDR2 400 it would be something like 2 chips of DDR200 working together to achieve the full 400 speed. Notice that I say "chips" not sticks of memory. All this happens on 1 stick of memory. In other words, when calculating in tandem in respect to the FSB, just divide the given speed by 2.
Example:
Assume my quad-core, quad-pumped FSB = 1066MHz.
This means my System Clock is 1066/4 = 266MHz.
My CPU is clocked at 1.6GHz = 266MHz * CPU MULTIPLIER.
This means my CPU MULTIPLIER must be 1600/266 = 6.
Now here are my options for DDR2:
(A) 533MHz/2 = 266MHz. This is an EXACT MATCH to my System Clock.
(B) 667MHz/2 = 333MHz. This is the next highest speed available.
(C) 800MHz/2 = 400MHz. This is pure overkill since the System Clock is capped at 266MHz.
In these stated cases, (B) is actually preferred. (A) is an exact match which means sometimes its lag can adversely affect the CPU bus speed. As stated, option (C) is overkill.
WEB: How to set up web-server w/ FiOS
Since Verizon blocks port 80, this is listed online as the only workaround. It entails targeting a different port (like 8015), and then using the Verizon FiOS router to re-route the request to the correct web server machine.
Furthermore, people used no-ip.com's dynamic dns service to automatically forward the url name requests like www.happy.com to www.happy.com:8015, thereby eliminating the ugliness of forcing your customers to specify the ports.
* Prior to following the steps in this guide to hosting your web server, make sure you read the Verizon ToS, which states the following:
You also may not exceed the bandwidth usage limitations that Verizon may establish from time to time for the Service, or use the Service to host any type of server. Violation of this section may result in bandwidth restrictions on your Service or suspension or termination of your Service.
That said, be careful and charging on :)
STEP 1: Goto URL http://192.168.1.1
STEP 2: By default, username = admin, password = password (or password1)
STEP 3: On the top navi-bar, select Firewall Settings
STEP 4: Click yes to proceed
STEP 5: Click on Port Forwarding on the left navi-bar
STEP 6: From that table list, click Add at the bottom
STEP 7: Fill out the following table...
STEP 7a: Networked Computer/Device = danny (actual device name works best, since IPs can be dynamic)
STEP 8: Add new protocol
STEP 9: WAN Connection Type: All Broadband Devices
STEP 10: Forward to Port: Specify - 80
STEP 11: When should this rule occur: Always
STEP 12: Click Apply to get out of the Edit Port Forwarding Rule page
STEP 13: Click Apply to get out of the Port Forwarding page
STEP 14: From an external computer, type http://YOUR.IP:8015/, should direct you to the web server.
Furthermore, people used no-ip.com's dynamic dns service to automatically forward the url name requests like www.happy.com to www.happy.com:8015, thereby eliminating the ugliness of forcing your customers to specify the ports.
* Prior to following the steps in this guide to hosting your web server, make sure you read the Verizon ToS, which states the following:
You also may not exceed the bandwidth usage limitations that Verizon may establish from time to time for the Service, or use the Service to host any type of server. Violation of this section may result in bandwidth restrictions on your Service or suspension or termination of your Service.
That said, be careful and charging on :)
STEP 1: Goto URL http://192.168.1.1
STEP 2: By default, username = admin, password = password (or password1)
STEP 3: On the top navi-bar, select Firewall Settings
STEP 4: Click yes to proceed
STEP 5: Click on Port Forwarding on the left navi-bar
STEP 6: From that table list, click Add at the bottom
STEP 7: Fill out the following table...
STEP 7a: Networked Computer/Device = danny (actual device name works best, since IPs can be dynamic)
STEP 8: Add new protocol
STEP 9: WAN Connection Type: All Broadband Devices
STEP 10: Forward to Port: Specify - 80
STEP 11: When should this rule occur: Always
STEP 12: Click Apply to get out of the Edit Port Forwarding Rule page
STEP 13: Click Apply to get out of the Port Forwarding page
STEP 14: From an external computer, type http://YOUR.IP:8015/, should direct you to the web server.
APACHE: Enabling Apache + PHP on OSX
Step 1. Menu Bar > Go > Go to Folder... > /private/etc/apache2
Step 2. Open httpd.conf with TextEditor
Step 3. Uncomment this line:
#LoadModule php5_module libexec/apache2/libphp5.so
Step 4. Save this file onto the desktop as "httpd.conf"
Step 5. Drag the "httpd.conf" file you just created into /private/etc/apache2
Step 6. Authenticate your privileges: enter your password
Step 7. Make a copy of /etc/php.ini.default onto your desktop
Step 8. Rename php.ini.default to php.ini (the copy on your desktop)
Step 9. Drag the "php.ini.default" file you just created into /private/etc
Step 10. Authenticate your privileges: enter your password
Step 11. Open System Preferences > Sharing > Web Sharing: ON (check this option)
To Test:
Step 12. Create info.php with the content:
Step 13. Save it to /Library/WebServer/Documents
Step 14. Goto http://localhost/info.php
To Publish using your HOME/Sites directory
Step 15. Create info.php with content:
Step 16. Save it to /Users/$MYNAME/Sites
Step 17. Goto http://$COMPUTERNAME.home/~$MYNAME/info.php
Step 2. Open httpd.conf with TextEditor
Step 3. Uncomment this line:
#LoadModule php5_module libexec/apache2/libphp5.so
Step 4. Save this file onto the desktop as "httpd.conf"
Step 5. Drag the "httpd.conf" file you just created into /private/etc/apache2
Step 6. Authenticate your privileges: enter your password
Step 7. Make a copy of /etc/php.ini.default onto your desktop
Step 8. Rename php.ini.default to php.ini (the copy on your desktop)
Step 9. Drag the "php.ini.default" file you just created into /private/etc
Step 10. Authenticate your privileges: enter your password
Step 11. Open System Preferences > Sharing > Web Sharing: ON (check this option)
To Test:
Step 12. Create info.php with the content:
Step 13. Save it to /Library/WebServer/Documents
Step 14. Goto http://localhost/info.php
To Publish using your HOME/Sites directory
Step 15. Create info.php with content:
Step 16. Save it to /Users/$MYNAME/Sites
Step 17. Goto http://$COMPUTERNAME.home/~$MYNAME/info.php
IPHONE: MySQL on iPhone
Before we go on, I'm going to assume you already know that the simplest way to achieve MySQL data connection is by writing a short scriptlet in PHP/JSP, etc. While simpler, it's security is somewhat problematic, since sniffers may be able to pick up the URL requests.
After hours of research I found what seems like the only solution: Cocoa-MySQL + MySQL C-API
According to this blog, all you seem to need is Cocoa-MySQL, but no matter what I tried, I just couldn't seem to get the binaries to link correctly. Not to mention, Apple has a pretty strict limitation on private frameworks, and this solution probably goes against one of their 20 NDAs.
This is where MySQL C-API comes in handy. I downloaded Mac OS X 10.5 (TAR package) for my x86 Intel system. Extract the zip and grab the /lib and /include folders and throw them into some local directory (NOT IN YOUR XCODEPROJ, see steps 4, 5 below).
From the Cocoa-MySQL site, download MCPKit_src_XXX.dmg, and grab the contents of /MCPFoundationKit and throw it into your XCODEPROJ. These are great wrapper classes that help facilitate the connection & query processes.
If you tried to build the app right now, you'd get errors stating missing headers and mysql_xxx_xxx functions. That's because we haven't set up the project settings yet.
1. In Xcode, goto Project > Edit Project Settings.
2. Select the Build tab.
3. Under Linking > Other Linking FLags, add the following flags: -lmysqlclient_r, -lmysqld, -lmysqlclient, -lm, -lz
4. Under Search Paths > Header Search Paths:
5. Under Search Paths > Library Search Paths:
6. Add #import "MCPKit_bundled.h" to the header of any class accessing MySQL
7. Edit MCPKit_bundled.h by changing all #import to #import "XXX.h"
Now you should be able to build, and use the sample code from the blog previously mentioned to directly connect to a remote MySQL server.
After hours of research I found what seems like the only solution: Cocoa-MySQL + MySQL C-API
According to this blog, all you seem to need is Cocoa-MySQL, but no matter what I tried, I just couldn't seem to get the binaries to link correctly. Not to mention, Apple has a pretty strict limitation on private frameworks, and this solution probably goes against one of their 20 NDAs.
This is where MySQL C-API comes in handy. I downloaded Mac OS X 10.5 (TAR package) for my x86 Intel system. Extract the zip and grab the /lib and /include folders and throw them into some local directory (NOT IN YOUR XCODEPROJ, see steps 4, 5 below).
From the Cocoa-MySQL site, download MCPKit_src_XXX.dmg, and grab the contents of /MCPFoundationKit and throw it into your XCODEPROJ. These are great wrapper classes that help facilitate the connection & query processes.
If you tried to build the app right now, you'd get errors stating missing headers and mysql_xxx_xxx functions. That's because we haven't set up the project settings yet.
1. In Xcode, goto Project > Edit Project Settings.
2. Select the Build tab.
3. Under Linking > Other Linking FLags, add the following flags: -lmysqlclient_r, -lmysqld, -lmysqlclient, -lm, -lz
4. Under Search Paths > Header Search Paths:
5. Under Search Paths > Library Search Paths:
7. Edit MCPKit_bundled.h by changing all #import
Now you should be able to build, and use the sample code from the blog previously mentioned to directly connect to a remote MySQL server.
IPHONE: IBAction and IBOutlet
Sometimes when all you need is a simple UI application that doesn't require too much customization or skinning, you can try building the application in Interface Builder.
Step 1: Create a New Project (Apple+Shift+N) > View-Based Application, name the application IBTest
Step 2: Edit the default IBTestViewController.h & .m files. Add the following lines in the appropriate places:
IBOutlet UIButton* button; IBOutlet UILabel* label; - (IBAction)userPressedButton:(id)sender;
Step 3: Open MainWindow.xib w/ Interface Builder
Step 4: Double-Click Test View Controller and a window will pop up
Step 5a: Add a View (from the library: APPLE+L) to Test View Controller
Step 5b: Add a Rounded Rect Button to the View you just added
Step 5c: Add a Label to the View you just added
Step 6: Link your UIButton & UILabel to the button and label you just added Apple+Right-Clicking the Rounded Rect Button & drag your mouse onto the Test View Controller
Step 7: Select userPressedButton in the popup
Done... your code is now hooked up through the interface builder. When users click the button, your userPressedButtons method will fire, as expected.
Step 1: Create a New Project (Apple+Shift+N) > View-Based Application, name the application IBTest
Step 2: Edit the default IBTestViewController.h & .m files
Step 3: Open MainWindow.xib w/ Interface Builder
Step 5b: Add a Rounded Rect Button to the View you just added
Step 5c: Add a Label to the View you just added
Step 7: Select userPressedButton in the popup
IPHONE: Removing the GLOSS from the app icon
Edit the Info.plist file...
UIPrerenderedIcon = true
In plain text:
UIPrerenderedIcon
UIPrerenderedIcon = true
In plain text:
IPHONE: Changing the Product Name
If your single source produces multiple 'products', ie. *.app's, it may be necessary to differentiate the 2 by designating the product names.
To create 2 products from 1 source:
- Create a new target by making a copy of the first.
- Modify this target by changing its Info.plist (by default will be Info Copy.plist)
- Modify its displayed name by changing its Infoplist.strings
- Optionally you can add a PREPROCCESSOR MACRO to differentiate the 2 targets (see previous post)
But when you compile the 2 targets, they always have the same .app name. This could be problematic for multiple reasons...
- If your bundle identifier is com.xxx.Application, your Product name should be 'Application'
- If you want to differentiate the 2 builds, it'd be easier if the 2 did not have the same app name
To do so:
- Highlight the Targets > Application 1
- Right click > Get Info
- Build tab
- Packaging > Product Name = New Application name
To create 2 products from 1 source:
- Create a new target by making a copy of the first.
- Modify this target by changing its Info.plist (by default will be Info Copy.plist)
- Modify its displayed name by changing its Infoplist.strings
- Optionally you can add a PREPROCCESSOR MACRO to differentiate the 2 targets (see previous post)
But when you compile the 2 targets, they always have the same .app name. This could be problematic for multiple reasons...
- If your bundle identifier is com.xxx.Application, your Product name should be 'Application'
- If you want to differentiate the 2 builds, it'd be easier if the 2 did not have the same app name
To do so:
- Highlight the Targets > Application 1
- Right click > Get Info
- Build tab
- Packaging > Product Name = New Application name
IPHONE: Environment Variables & #define directives
To use Configuration-defined #defines
Step 1: Right click on the project/target and select Get Info.
Step 2: Under the Build tab, select the Configuration you want to associate the #define with (ie. Debug/Release)
Step 3: Under User-Defined (Setting) all the way at the bottom, find a field that's called
GCC_PREPROCESSOR_DEFINITIONS
Step 4: If a field doesn't already exist, create it by clicking on the Gear on the bottom left & selecting Add User-Defined Setting.
Step 5: For the VALUE, input your #define variable. (ie. TEST_DEFINES)
Step 6: Now in code you can use
#ifdef TEST_DEFINES
... do something
#else
... do something
#endif
Step 1: Right click on the project/target and select Get Info.
Step 2: Under the Build tab, select the Configuration you want to associate the #define with (ie. Debug/Release)
Step 3: Under User-Defined (Setting) all the way at the bottom, find a field that's called
GCC_PREPROCESSOR_DEFINITIONS
Step 4: If a field doesn't already exist, create it by clicking on the Gear on the bottom left & selecting Add User-Defined Setting.
Step 5: For the VALUE, input your #define variable. (ie. TEST_DEFINES)
Step 6: Now in code you can use
#ifdef TEST_DEFINES
... do something
#else
... do something
#endif
Tomcat: Starting tomcat in Mac OSX
When http://localhost:8080 isn't working, you may want to try starting the tomcat server.
I'm going to assume that Tomcat was installed at /Library/Tomcat/apache-tomcat-6.0.18/
cd /Library/Tomcat/apache-tomcat-6.0.18/bin
./startup.sh
p.s. During setup, make sure CATALINA_HOME points to /Library/Tomcat/apache-tomcat-6.0.18. If it is not, edit your .profile file and redirect the CATALINA_HOME environment variable.
I'm going to assume that Tomcat was installed at /Library/Tomcat/apache-tomcat-6.0.18/
cd /Library/Tomcat/apache-tomcat-6.0.18/bin
./startup.sh
p.s. During setup, make sure CATALINA_HOME points to /Library/Tomcat/apache-tomcat-6.0.18. If it is not, edit your .profile file and redirect the CATALINA_HOME environment variable.
iPhone: Localization
Should have done my research before trying to do my own localization on the phone... the full article can be found here. Here are the basic steps to localizing your iphone application. Trust me, this is the way to do it...
Step 1: Create 2 directories called en.lproj (English) and it.lproj (Italian)
Step 2: Add new string file by going to File -> New File -> Other -> Strings File, name the file as "Localizable.strings" and place it in en.lproj.
Step 3: Repeat step 2, this time saving "Localizable.strings" inside it.lproj.
Step 4: Add the following lines to the strings files...
Step 5: To grab WelcomeKey you just do: NSLocalizedString(@"WelcomeKey", @"") like so:
That's all there is to it... Here are some of Apple's conventional language codes:
English: en
Japanese: ja
French: fr
Deutsch: de
Netherlands: nl
Italian: it
Spanish: es
Portugues: pt
Korean: ko
Simplified Chinese: zh-Hans
Traditional Chinese: zh-Hant
The full list can be accessed through the following call:
Step 1: Create 2 directories called en.lproj (English) and it.lproj (Italian)
Step 2: Add new string file by going to File -> New File -> Other -> Strings File, name the file as "Localizable.strings" and place it in en.lproj.
Step 3: Repeat step 2, this time saving "Localizable.strings" inside it.lproj.
Step 4: Add the following lines to the strings files...
"WelcomeKey" = "Welcome!!!"; // put into english version
"WelcomeKey" = "Benvenuto!!!"; // put into italian versionStep 5: To grab WelcomeKey you just do: NSLocalizedString(@"WelcomeKey", @"") like so:
NSLog(@"Welcome Text: %@", NSLocalizedString(@"WelcomeKey", @""));
That's all there is to it... Here are some of Apple's conventional language codes:
English: en
Japanese: ja
French: fr
Deutsch: de
Netherlands: nl
Italian: it
Spanish: es
Portugues: pt
Korean: ko
Simplified Chinese: zh-Hans
Traditional Chinese: zh-Hant
The full list can be accessed through the following call:
NSArray *languages = [defaults objectForKey:@"AppleLanguages"];
// print each NSString in languages
PostgreSQL: Advanced PostgreSQL
Transactions:
begin work;
// do query
commit work;
begin work;
// do query
rollback work; // undo
begin work;
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE; // serialize, data doesn't change
// do query
commit work;
begin work;
// do query. End with FOR UPDATE; this serializes & locks this transaction until I update or transaction ends
// do update
commit work;
INDEX: Speeds up searches
create index [indexname] on [tbl] ( [col1], [col2] );
drop index [indexname];
create unique index [indexname] on [tbl] ( [col1], [col2] );
CLUSTER: Speeds up searches by clustering large search results
VACUUM: Speeds up searches by cleaning up expired rows
vacuum [tbl];
vacuum analyze [tbl];
EXPLAIN: Shows speed & statistic on queries
explain select * from [tbl];
LIMIT:
select * from [tbl] limit #;
select * from [tbl] limit # offset #;
CURSOR: must take place inside a transaction
begin work;
declare [cursor name] cursor for select [col] from [tbl];
fetch # from [cursor name];
move #from [cursor name];
close [cursor name];
commit work;
Temporary tables
select * into temporary [tbl] from [tbl2] where [condition];
Alter table content:
alter table [tbl] rename to [tbl'];
alter table [tbl] rename column [col] to [col'];
alter table [tbl] add column [col] [type];
alter table [tbl] alter column [col] [type];
alter table [tbl] alter column [col] set default [value];
alter table [tbl] alter column [col] drop default;
Grant permission:
grant select on [tbl] to [user];
grant all on [tbl] to public;
Inheritance:
create table [tbl] ( ... );
create table [tb2] ( ... ) inherits ( [tbl1] );
select * from [tbl1]*; // access shared columns in tbl1 & tbl2
Views: Views cannot be directly modified, just queried
create view [viewname] as [select ...];
drop view [viewname];
Rules:
create rule [rulename] as on select to [tbl/view] do instead nothing;
create rule [rulename] as on insert to [tbl/view] do instead [what to do];
create rule [rulename] as on update to [tbl/view] do instead [what to do];
create rule [rulename] as on deleete to [tbl/view] do instead [what to do];
Constraints: NOT NULL, UNIQUE, PRIMARY KEY
create table [tbl] ( col1 INTEGER NOT NULL DEFAULT [value] );
create table [tbl] ( col1 INTEGER UNIQUE );
create table [tbl] ( col1 INTEGER PRIMARY KEY ); // UNIQUE+NOT NULL
create table [tbl] (
col1 INTEGER,
col2 INTEGER,
UNIQUE(col1, col2) // must be on its own line
);
create table [tbl] (
col1 INTEGER,
col2 INTEGER,
PRIMARY KEY(col1, col2) // must be on its own line
);
Foreign Key:
create table [tbl1] ( col INTEGER PRIMARY KEY );
create table [tbl2] ( col INTEGER REFERENCES [tbl1] );
Foreign Key Options:
create table [tbl2] ( col INTEGER REFERENCES [tbl1] on update CASCADE on delete SET NULL );
where:
NO ACTION = UPDATEs and DELETEs to the primary key are prohibited if referenced by a foreign key row. (Default)
CASCADE = UPDATEs to the primary key update all foreign key columns that reference it. DELETEs on the primary key cause the deletion of all foreign key rows that reference it.
SET NULL = UPDATEs and DELETEs to the primary key row cause the foreign key to be set to NULL.
CHECK: validity checking during insertion
create table [tbl] ( age INTEGER CHECK (age > 18) );
create table [tbl] ( gender CHAR(1) CHECK (gender IN ('M', 'F') );
create table [tbl] ( age INTEGER, gender CHAR(1), CHECK ( age > 18 and gender in ('M', 'F') ) );
begin work;
// do query
commit work;
begin work;
// do query
rollback work; // undo
begin work;
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE; // serialize, data doesn't change
// do query
commit work;
begin work;
// do query. End with FOR UPDATE; this serializes & locks this transaction until I update or transaction ends
// do update
commit work;
INDEX: Speeds up searches
create index [indexname] on [tbl] ( [col1], [col2] );
drop index [indexname];
create unique index [indexname] on [tbl] ( [col1], [col2] );
CLUSTER: Speeds up searches by clustering large search results
VACUUM: Speeds up searches by cleaning up expired rows
vacuum [tbl];
vacuum analyze [tbl];
EXPLAIN: Shows speed & statistic on queries
explain select * from [tbl];
LIMIT:
select * from [tbl] limit #;
select * from [tbl] limit # offset #;
CURSOR: must take place inside a transaction
begin work;
declare [cursor name] cursor for select [col] from [tbl];
fetch # from [cursor name];
move #from [cursor name];
close [cursor name];
commit work;
Temporary tables
select * into temporary [tbl] from [tbl2] where [condition];
Alter table content:
alter table [tbl] rename to [tbl'];
alter table [tbl] rename column [col] to [col'];
alter table [tbl] add column [col] [type];
alter table [tbl] alter column [col] [type];
alter table [tbl] alter column [col] set default [value];
alter table [tbl] alter column [col] drop default;
Grant permission:
grant select on [tbl] to [user];
grant all on [tbl] to public;
Inheritance:
create table [tbl] ( ... );
create table [tb2] ( ... ) inherits ( [tbl1] );
select * from [tbl1]*; // access shared columns in tbl1 & tbl2
Views: Views cannot be directly modified, just queried
create view [viewname] as [select ...];
drop view [viewname];
Rules:
create rule [rulename] as on select to [tbl/view] do instead nothing;
create rule [rulename] as on insert to [tbl/view] do instead [what to do];
create rule [rulename] as on update to [tbl/view] do instead [what to do];
create rule [rulename] as on deleete to [tbl/view] do instead [what to do];
Constraints: NOT NULL, UNIQUE, PRIMARY KEY
create table [tbl] ( col1 INTEGER NOT NULL DEFAULT [value] );
create table [tbl] ( col1 INTEGER UNIQUE );
create table [tbl] ( col1 INTEGER PRIMARY KEY ); // UNIQUE+NOT NULL
create table [tbl] (
col1 INTEGER,
col2 INTEGER,
UNIQUE(col1, col2) // must be on its own line
);
create table [tbl] (
col1 INTEGER,
col2 INTEGER,
PRIMARY KEY(col1, col2) // must be on its own line
);
Foreign Key:
create table [tbl1] ( col INTEGER PRIMARY KEY );
create table [tbl2] ( col INTEGER REFERENCES [tbl1] );
Foreign Key Options:
create table [tbl2] ( col INTEGER REFERENCES [tbl1] on update CASCADE on delete SET NULL );
where:
NO ACTION = UPDATEs and DELETEs to the primary key are prohibited if referenced by a foreign key row. (Default)
CASCADE = UPDATEs to the primary key update all foreign key columns that reference it. DELETEs on the primary key cause the deletion of all foreign key rows that reference it.
SET NULL = UPDATEs and DELETEs to the primary key row cause the foreign key to be set to NULL.
CHECK: validity checking during insertion
create table [tbl] ( age INTEGER CHECK (age > 18) );
create table [tbl] ( gender CHAR(1) CHECK (gender IN ('M', 'F') );
create table [tbl] ( age INTEGER, gender CHAR(1), CHECK ( age > 18 and gender in ('M', 'F') ) );
Subscribe to:
Posts (Atom)