![]() Importing your production database into the support environment is a simply import - no need to even drop existing values unless it is a performance problem (in which case, you don't want to change the data distribution). ![]() Even more importantly, a UUID for a USER in your production environment will not collide with the UUID for a USER in your production support environment. A UUID in your USER table is distinct from a UUID in your ORG table. That means that there should never be a collision between tables. UUIDs have the benefit of being "Universally Unique". And for the first time, someone answered the question intelligently and won me over. When i joined Altisource, lo and behold, all of the PKs in the proposed data model were CHAR(36). So, I let it drop (I had more urgent things to do). However, when I asked why, they weren't able to answer the question or to tell me who made the choice. Seems like a lot of overhead, if you ask me. It seemed like an odd choice - a 36-byte string rather than a 4- or 8-byte integer number. I had worked with UUIDs as primary keys before, when I was a short-term contractor a while back. Our project is using JPA to do the mappings and Hibernate as the Entity Provider. Just about everyone knows what JPA is- the Sun-standardized way to perform Object Relational Mapping. They also have a subproject to make JPA easier to use. Each of the subprojects is fairly individual from each other, because each of these data technologies has a different way of doing business, but they bring standard Spring-isms like dependency injection and Template-based access. I have always heard it coupled with technologies like redis, Hadoop, and MongoDB. The Spring Data project makes it easier to integrate Spring projects with new data technologies. It has been very busy at work, which has kept me from writing, and I have moved from working in Grails to working directly in a lot of different Spring, including Spring Security, Spring Integration, and something new for me, Spring Data JPA.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |