search

kcigeospatial / balt_co_ETL

This will provide a place to track internal issues around the Baltimore County NPDES NCT application ETL.
0 stars 0 forks source link

MDE export does not contain relationships #40

Closed leeensminger closed 6 years ago

leeensminger commented 6 years ago

The MDE export does not contain the explicit relationship classes found in the template. Is it feasible to include this, or is there a reason why we could not achieve this?

gerrykelly commented 6 years ago

The relationship classes were missing because of the way I needed to copy objects to avoid schema locking issues and I could not find a way around it. Since you can't simply copy RCs from one GDB to another I needed to write a routine that loops through all the RCs in the MDE template, reads their properties then creates them in the output GDB (if one or both of the involved objects does not exist in the output -- as is the case on append failures -- then you will get a message that the RC could not be created. Test after my next GP service update.

BC89 commented 6 years ago

Can't we simply put the relationship classes in the templates db and be done with it?

Sent from my Samsung Galaxy , an AT&T LTE smartphone

-------- Original message -------- From: Gerry Kelly notifications@github.com Date: 12/12/17 6:07 PM (GMT-05:00) To: kcigeospatial/balt_co_ETL balt_co_ETL@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: Re: [kcigeospatial/balt_co_ETL] MDE export does not contain relationships (#40)

The relationship classes were missing because of the way I needed to copy objects to avoid schema locking issues and I could not find a way around it. Since you can't simply copy RCs from one GDB to another I needed to write a routine that loops through all the RCs in the MDE template, reads their properties then creates them in the output GDB (if one or both of the involved objects does not exist in the output -- as is the case on append failures -- then you will get a message that the RC could not be created. Test after my next GP service update.

- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/kcigeospatial/balt_co_ETL/issues/40#issuecomment-351225360, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADJUMw701Pf1hJARsKqBHFhACdzdU6qpks5s_wdggaJpZM4Q8iQI.

gerrykelly commented 6 years ago

@BC89 @leeensminger With how the ETL works now, I think I need to use the routine I wrote yesterday and it works fine (but let's verify).

leeensminger commented 6 years ago

@gerrykelly where did we leave off with this? are relationships to be expected in the output? they are not currently.

gerrykelly commented 6 years ago

@leeensminger This should be working but I had deactivated the code for testing and forgot to put it back in (the all-messages log file from your runs have had a message "skipping relationship classes RESTORE later" in it -- as a reminder to me)

leeensminger commented 6 years ago

Appears OK