General information
Category:
Databases,Tables, Views, Indexing and SQL syntax
>>In this scenario you have to create the PK in the view. I use views mostly for children tables, so I did not thought about this.
>I store the PK in a separate table, so I don't need GUIDs. If I create twice the PK (in the table and in the view), I thought I was wasting PKs; to my surprise it was not the case. I have to research deeper to know why didn't VFP created twice the PK.
>Besides, I was not really concerned about wasting PK, as with an integer type I get 4 billion PK (including negative integers).
>
>The reason you are not wasting primary keys is that the code to create a primary key doesn't fire unless the field is empty.
>
>Regards,
>
>Jim
I did not know that when the view updates its tables default values methods did not fire if the view provided a value for those fields. Good to know that.
Thanks a lot,
Javier.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only