Jump to content

This topic is 5203 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

I have recently begun converting the primary keys in our solution to Ray Cologon's base36 UUIDs. I've played around with some of the file options to determine the best behavior for these fields, but I'm not quite settled on what is optimum. For example, if I check don't replace existing values, duplicating a record carries the Id to the duplicate. Obviously bad. However, it looks like without checking this, importing records into the database and selecting perform auto enter options would change the key values. Not a problem if you don't perform the auto enter options, but if you have other fields that need these auto options performed produces a conflict.

Just curious about other developer insights into the file options and proper usage of these things.

Thanks for your thoughts.

This topic is 5203 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.