- Văn bản
- Lịch sử
ng for . We could go through the da
ng for .
We could go through the database and adjust all the Employeeentities to have their correct type, but
if the employee type is used elsewhere, then we would need to make sure that they were all fixed as
well. This is not a good maintenance situation to be in.
A better solution would be to store the name of the value as a string instead of storing the ordinal.
This would isolate us from any changes in declaration and allow us to add new types without having to
worry about the existing data. We can do this by adding an @Enumeratedannotation on the attribute and
specifying a value of STRING.
The @Enumeratedannotation actually allows an EnumTypeto be specified, and the EnumTypeis itself
an enumerated type that defines values of ORDINALand STRING. While it is somewhat ironic that an
enumerated type is being used to indicate how the provider should represent enumerated types, it is
wholly appropriate. Because the default value of @Enumeratedis ORDINAL, specifying
@Enumerated(ORDINAL)is useful only when you want to make this mapping explicit.
In Listing 4-11, we are storing strings for the enumerated values. Now the TYPEcolumn must be a
string-based type, and all of the full-time employees will have the string “FULL_TIME_EMPLOYEE”
stored in their corresponding TYPEcolumn.
We could go through the database and adjust all the Employeeentities to have their correct type, but
if the employee type is used elsewhere, then we would need to make sure that they were all fixed as
well. This is not a good maintenance situation to be in.
A better solution would be to store the name of the value as a string instead of storing the ordinal.
This would isolate us from any changes in declaration and allow us to add new types without having to
worry about the existing data. We can do this by adding an @Enumeratedannotation on the attribute and
specifying a value of STRING.
The @Enumeratedannotation actually allows an EnumTypeto be specified, and the EnumTypeis itself
an enumerated type that defines values of ORDINALand STRING. While it is somewhat ironic that an
enumerated type is being used to indicate how the provider should represent enumerated types, it is
wholly appropriate. Because the default value of @Enumeratedis ORDINAL, specifying
@Enumerated(ORDINAL)is useful only when you want to make this mapping explicit.
In Listing 4-11, we are storing strings for the enumerated values. Now the TYPEcolumn must be a
string-based type, and all of the full-time employees will have the string “FULL_TIME_EMPLOYEE”
stored in their corresponding TYPEcolumn.
0/5000
ng for .
We could go through the database and adjust all the Employeeentities to have their correct type, but
if the employee type is used elsewhere, then we would need to make sure that they were all fixed as
well. This is not a good maintenance situation to be in.
A better solution would be to store the name of the value as a string instead of storing the ordinal.
This would isolate us from any changes in declaration and allow us to add new types without having to
worry about the existing data. We can do this by adding an @Enumeratedannotation on the attribute and
specifying a value of STRING.
The @Enumeratedannotation actually allows an EnumTypeto be specified, and the EnumTypeis itself
an enumerated type that defines values of ORDINALand STRING. While it is somewhat ironic that an
enumerated type is being used to indicate how the provider should represent enumerated types, it is
wholly appropriate. Because the default value of @Enumeratedis ORDINAL, specifying
@Enumerated(ORDINAL)is useful only when you want to make this mapping explicit.
In Listing 4-11, we are storing strings for the enumerated values. Now the TYPEcolumn must be a
string-based type, and all of the full-time employees will have the string “FULL_TIME_EMPLOYEE”
stored in their corresponding TYPEcolumn.
We could go through the database and adjust all the Employeeentities to have their correct type, but
if the employee type is used elsewhere, then we would need to make sure that they were all fixed as
well. This is not a good maintenance situation to be in.
A better solution would be to store the name of the value as a string instead of storing the ordinal.
This would isolate us from any changes in declaration and allow us to add new types without having to
worry about the existing data. We can do this by adding an @Enumeratedannotation on the attribute and
specifying a value of STRING.
The @Enumeratedannotation actually allows an EnumTypeto be specified, and the EnumTypeis itself
an enumerated type that defines values of ORDINALand STRING. While it is somewhat ironic that an
enumerated type is being used to indicate how the provider should represent enumerated types, it is
wholly appropriate. Because the default value of @Enumeratedis ORDINAL, specifying
@Enumerated(ORDINAL)is useful only when you want to make this mapping explicit.
In Listing 4-11, we are storing strings for the enumerated values. Now the TYPEcolumn must be a
string-based type, and all of the full-time employees will have the string “FULL_TIME_EMPLOYEE”
stored in their corresponding TYPEcolumn.
đang được dịch, vui lòng đợi..
ng for .
We could go through the database and adjust all the Employeeentities to have their correct type, but
if the employee type is used elsewhere, then we would need to make sure that they were all fixed as
well. This is not a good maintenance situation to be in.
A better solution would be to store the name of the value as a string instead of storing the ordinal.
This would isolate us from any changes in declaration and allow us to add new types without having to
worry about the existing data. We can do this by adding an @Enumeratedannotation on the attribute and
specifying a value of STRING.
The @Enumeratedannotation actually allows an EnumTypeto be specified, and the EnumTypeis itself
an enumerated type that defines values of ORDINALand STRING. While it is somewhat ironic that an
enumerated type is being used to indicate how the provider should represent enumerated types, it is
wholly appropriate. Because the default value of @Enumeratedis ORDINAL, specifying
@Enumerated(ORDINAL)is useful only when you want to make this mapping explicit.
In Listing 4-11, we are storing strings for the enumerated values. Now the TYPEcolumn must be a
string-based type, and all of the full-time employees will have the string “FULL_TIME_EMPLOYEE”
stored in their corresponding TYPEcolumn.
We could go through the database and adjust all the Employeeentities to have their correct type, but
if the employee type is used elsewhere, then we would need to make sure that they were all fixed as
well. This is not a good maintenance situation to be in.
A better solution would be to store the name of the value as a string instead of storing the ordinal.
This would isolate us from any changes in declaration and allow us to add new types without having to
worry about the existing data. We can do this by adding an @Enumeratedannotation on the attribute and
specifying a value of STRING.
The @Enumeratedannotation actually allows an EnumTypeto be specified, and the EnumTypeis itself
an enumerated type that defines values of ORDINALand STRING. While it is somewhat ironic that an
enumerated type is being used to indicate how the provider should represent enumerated types, it is
wholly appropriate. Because the default value of @Enumeratedis ORDINAL, specifying
@Enumerated(ORDINAL)is useful only when you want to make this mapping explicit.
In Listing 4-11, we are storing strings for the enumerated values. Now the TYPEcolumn must be a
string-based type, and all of the full-time employees will have the string “FULL_TIME_EMPLOYEE”
stored in their corresponding TYPEcolumn.
đang được dịch, vui lòng đợi..
Các ngôn ngữ khác
Hỗ trợ công cụ dịch thuật: Albania, Amharic, Anh, Armenia, Azerbaijan, Ba Lan, Ba Tư, Bantu, Basque, Belarus, Bengal, Bosnia, Bulgaria, Bồ Đào Nha, Catalan, Cebuano, Chichewa, Corsi, Creole (Haiti), Croatia, Do Thái, Estonia, Filipino, Frisia, Gael Scotland, Galicia, George, Gujarat, Hausa, Hawaii, Hindi, Hmong, Hungary, Hy Lạp, Hà Lan, Hà Lan (Nam Phi), Hàn, Iceland, Igbo, Ireland, Java, Kannada, Kazakh, Khmer, Kinyarwanda, Klingon, Kurd, Kyrgyz, Latinh, Latvia, Litva, Luxembourg, Lào, Macedonia, Malagasy, Malayalam, Malta, Maori, Marathi, Myanmar, Mã Lai, Mông Cổ, Na Uy, Nepal, Nga, Nhật, Odia (Oriya), Pashto, Pháp, Phát hiện ngôn ngữ, Phần Lan, Punjab, Quốc tế ngữ, Rumani, Samoa, Serbia, Sesotho, Shona, Sindhi, Sinhala, Slovak, Slovenia, Somali, Sunda, Swahili, Séc, Tajik, Tamil, Tatar, Telugu, Thái, Thổ Nhĩ Kỳ, Thụy Điển, Tiếng Indonesia, Tiếng Ý, Trung, Trung (Phồn thể), Turkmen, Tây Ban Nha, Ukraina, Urdu, Uyghur, Uzbek, Việt, Xứ Wales, Yiddish, Yoruba, Zulu, Đan Mạch, Đức, Ả Rập, dịch ngôn ngữ.
- Quality assurance/quality control guidel
- nhà tôi gần nó bãi rác nhất
- nó luôn trung thành, đáng tin cậy và khô
- mỗi ngày trôi qua
- kỉ niệm học trò
- The most flexible and portable way to ge
- We mentioned above that a particle can b
- nơi để rác
- When persisting a field or property, the
- tôi đang nghe nhạctôi mới chụp ảnh đó
- It's hard to say because you're not usin
- MARKETINGBAR & BEVERAGE OPERATIONS 1.WHA
- When persisting a field or property, the
- I miss you
- nhưng tôi không có tiền dẫn bạn đi chơi
- TECHNOLOGY INFRASTRUCTURE MANAGEMENT"Acc
- Casilda in Act I, which, so far as we co
- We mentioned above that a particle can b
- but I have no money to go out or lead yo
- I like to wear jum suit
- Many databases support an internal mecha
- but I don't have the money to take you o
- @tiniiz: เวลากลับตะลาปัด 5555 #พิมพืดแน่
- LIBRARY INFORMATION TECHNOLOGY
