Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Simulating multiple tables
Message
 
 
General information
Forum:
Microsoft SQL Server
Category:
Database design
Environment versions
SQL Server:
SQL Server 2005
Miscellaneous
Thread ID:
01410856
Message ID:
01410902
Views:
29
>>Can you post what you tried already?
>>
>>To me this sounds like
>>
>>trigger body
>>
>>insert into mySecondTable select ID, some other info from Inserted
>
>This works - but requires a ProductFileId field in ProductFileData:
    DECLARE @rowid uniqueidentifier
>    SET @rowid = NEWID()
>    INSERT INTO ProductFileData
>    (ProductFileColumnId,ProductFileRowId,ProductFileId)
>    SELECT INSERTED.Id,@rowid,INSERTED.ProductFileId
>    FROM INSERTED INNER JOIN ProductFileData ON ProductFileData.ProductFileId = INSERTED.ProductFileId
>
>UPDATE: On second thoughts - it doesn't - I need unique row IDs.....

Exactly - I was going to tell that it's not going to work this way because of multiple inserts possibility.

But would this work?
    INSERT INTO ProductFileData
    (ProductFileColumnId,ProductFileRowId,ProductFileId)
    SELECT INSERTED.Id,NewID(),INSERTED.ProductFileId
    FROM INSERTED INNER JOIN ProductFileData ON ProductFileData.ProductFileId = INSERTED.ProductFileId
Or why not let ProductFileRowID field to have default NewID() and then you don't need to include it in insert?
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform