Privacy Policy
The privacy of our visitors to http://thegioitinhoccuatoi.blogspot.com is important to us.
At http://thegioitinhoccuatoi.blogspot.com, we recognize that privacy of your personal information is important. Here is information on what types of personal information we receive and collect when you use visit http://thegioitinhoccuatoi.blogspot.com, and how we safeguard your information. We never sell your personal information to third parties.
Log Files
As with most other websites, we collect and use the data contained in log files. The information in the log files include your IP (internet protocal) address, your ISP (internet service provider, such as AOL or Shaw Cable), the browser you used to visit our site (such as Internet Explorer or Firefox), the time you visited our site and which pages you visited throughout our site.
Cookies and Web Beacons
We do use cookies to store information, such as your personal preferences when you visit our site. This could include only showing you a popup once in your visit, or the ability to login to some of our features, such as forums.
We also use third party advertisements on http://thegioitinhoccuatoi.blogspot.com to support our site. Some of these advertisers may use technology such as cookies and web beacons when they advertise on our site, which will also send these advertisers (such as Google through the Google AdSense program) information including your IP address, your ISP , the browser you used to visit our site, and in some cases, whether you have Flash installed. This is generally used for geotargeting purposes (showing New York real estate ads to someone in New York, for example) or showing certain ads based on specific sites visited (such as showing cooking ads to someone who frequents cooking sites).
You can chose to disable or selectively turn off our cookies or third-party cookies in your browser settings, or by managing preferences in programs such as Norton Internet Security. However, this can affect how you are able to interact with our site as well as other websites. This could include the inability to login to services or programs, such as logging into forums or accounts.
Contact Information
If users have any questions or suggestions regarding our privacy policy, please contact me through my contact form or send me an email to: testoldfriend(at) yahoo (dot) com.
Saturday, March 8, 2008
Privacy Policy
Posted by CABA LAM at 6:41 PM 1 comments
Friday, March 7, 2008
Hibernate, JBoss and auto-increment field
The
This is the optional element under
In this case
Here are the list of some commonly used generators in hibernate:
Generator | Description |
increment | It generates identifiers of type long, short or int that are unique only when no other process is inserting data into the same table. It should not the used in the clustered environment. |
identity | It supports identity columns in DB2, MySql, MS SQL Server, Sybase and HypersonicSQL. The returned identifier is of type long, short or int. |
sequence | The sequence generator uses a sequence in DB2, PostgreSQL, Oracle, SAP DB, McKoi or a generator in Interbase. The returned identifier is of type long, short or int |
hilo | The hilo generator uses a hi/lo algorithm to efficiently generate identifiers of type long, short or int, given a table and column (by default hibernate_unique_key and next_hi respectively) as a source of hi values. The hi/lo algorithm generates identifiers that are unique only for a particular database. Do not use this generator with connections enlisted with JTA or with a user-supplied connection. |
seqhilo | The seqhilo generator uses a hi/lo algorithm to efficiently generate identifiers of type long, short or int, given a named database sequence. |
uuid | The uuid generator uses a 128-bit UUID algorithm to generate identifiers of type string, unique within a network (the IP address is used). The UUID is encoded as a string of hexadecimal digits of length 32. |
guid | It uses a database-generated GUID string on MS SQL Server and MySQL. |
native | It picks identity, sequence or hilo depending upon the capabilities of the underlying database. |
assigned | lets the application to assign an identifier to the object before save() is called. This is the default strategy if no |
select | retrieves a primary key assigned by a database trigger by selecting the row by some unique key and retrieving the primary key value. |
foreign | uses the identifier of another associated object. Usually used in conjunction with a |
Therefore,
If your application is EJB, WS which create multiple threads, you should not use class=increment. Instead, you should use class=sequence or native. Or you will
encounter the problem: unique constrain violation.
Posted by CABA LAM at 10:20 PM 0 comments
Subscribe to:
Posts (Atom)