Thanks Tim. I'll go back to the user and ask them if they know anything- it certainly would be interesting to know what's generating them given it's not dspace- but I've gone far enough through the process to feel confident that deleting them will allow the migration to take place.
Cheers Scott On Monday, January 29, 2018 at 8:31:31 PM UTC, Tim Donohue wrote: > > Hi Scott, > > Those views are not generated by DSpace (as far as I'm aware). Searching > Github does not show them in our codebase (and all views created by DSpace > are documented in our SQL database scripts). So, my best guess is that > these were locally created, or someone installed a custom Statistics plugin > in your DSpace that uses those? I notice they all start with "stats.", so > that's why I wonder if these are related either to a third-party plugin, or > were created locally to help run some detailed statistics on your DSpace. > > That's my best guess. If they are from a plugin, then hopefully someone > else on this list will recognize these names and report back. > > In any case, I don't see any harm to your DSpace in deleting them. But, > obviously, you may want to check to see if anyone knows why they were > created in the first place. > > Tim > > On Mon, Jan 29, 2018 at 2:19 PM Scott Renton <rent...@gmail.com > <javascript:>> wrote: > >> Hi folks, >> >> I see this was mentioned before in >> http://dspace.2283337.n4.nabble.com/Upgrade-3-2-to-5-4-database-problem-td4680533.html >> >> Basically, we are migrating from 4.2 to 5.6, and have hit database >> migrations problems between the 5.0.2014.09.25 and 5.0.2014.09.26 stages. >> Just like the above problem, it was down to stats related views: the first >> two it complained about (v_stats_workflow and stats.v_workflow) had only 6 >> lines in each, so I cheerfully hived them off and dropped. I'm now through >> to my next problem: >> >> Caused by: org.postgresql.util.PSQLException: ERROR: cannot drop table >> bundle column name because other objects depend on it >> >> Detail: view stats.v_files depends on table bundle column name >> >> view stats.v_files_coll depends on view stats.v_files >> >> view stats.v_files_comm depends on view stats.v_files >> >> view stats.v_item2bitstream depends on table bundle column name >> >> >> These views have a lot more in them. I'm all for dropping them, but >> wondered if anyone could advise on implications. I guess they are dspace >> generated- this is one of our least configured sites, so I'm guessing >> they've happened through user interaction rather than anything we've done. >> The one site we have that has gone to 5.6 didn't have these views. >> >> >> Cheers >> >> Scott >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to dspace-tech...@googlegroups.com <javascript:>. >> To post to this group, send email to dspac...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To post to this group, send email to dspace-tech@googlegroups.com. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
