Hi Agustina, I believe that issue was already fixed in 6.0 via this PR: https://github.com/DSpace/DSpace/pull/1454 (I think that code comment you linked to is outdated and somehow was never removed.)
My best guess is that those null values were created in your DSpace 5 site... then they were brought over to DSpace 7 via the upgrade. If somehow you've found a way to *create more* of these null values in DSpace 7, then that'd definitely be an unknown bug. I'm not aware of a way to do this (and I ran some quick tests on my local DSpace 7 and I'm not seeing it happen there). Tim On Thursday, April 21, 2022 at 5:47:32 AM UTC-5 Agustina Martinez wrote: > Dear all, > > I only happened to notice this in our database very recently as part of > our DSpace 7 testing: when running the following query: > > // DSpace 5 > select * from resourcepolicy where resource_id is null; > // DSpace 7 > select * from resourcepolicy where dspace_object is null; > > we have more than 30k rows with null values for all columns in the > resourcepolicy table. > > I thought this was maybe something from the migration to dspace 7 from our > dspace5 instance but no, it something that has been there for a long time > now. > > The only thing I could find out giving any hints is > https://github.com/DSpace/DSpace/blob/a9edca7f55e297afdac8835de31114a2ad911a22/dspace-api/src/main/java/org/dspace/content/ItemServiceImpl.java#L1042 > > > where there is a comment about this issue. > > Were people aware of this? Is this going to be fixed soon? > > Best, > Agustina > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/6dfb53f7-374a-47da-9100-bfbb9ad62304n%40googlegroups.com.
