It's possible to override Entity field in tests ??

[smaelc]

It's possible to overrides Entity column options ?
I have two classes:

@Setter
@Getter
@Entity(name="post_post")
public class PostEntity {

    // ...

    @CreatedBy
    @Column(name = "created_by", nullable = false, insertable = false, updatable = false)
    UUID createdBy;

    @LastModifiedBy
    @Column(name = "updated_by", nullable = false, insertable = false, updatable = false)
    UUID updatedBy;

}

@DataJpaTest
@ActiveProfiles("qa")
class PersistPostIT {

@Test
@Disable // You have to remove these lines in PostEntity before ", nullable = false, insertable = false, updatable = false"
void shouldSuccesssfullyPersist(){}
}

In META-INF/orm-test.xml

<?xml version="1.0" encoding="UTF-8"?>
<entity-mappings
        xmlns="https://jakarta.ee/xml/ns/persistence/orm"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="https://jakarta.ee/xml/ns/persistence/orm
                            https://jakarta.ee/xml/ns/persistence/orm_3_0.xsd"
        version="3.0">

    <entity class="com.example.PostEntity" access="FIELD">

        <table name="PostEntity" schema="public"/>

        <attributes>

            <basic name="createdBy">
                <column name="created_by" insertable="true" updatable="true" nullable="false"/>
            </basic>

            <basic name="updatedBy">
                <column name="updated_by" insertable="true" updatable="true" nullable="true"/>
            </basic>
        </attributes>
    </entity>
</entity-mappings>

The options in application-qa.yaml to call orm-test.xml or more ? I have no idea.

Stackoverflow origin question: https://stackoverflow.com/questions/79840437/how-to-overrides-entity-field-in-tests-with-spring-boot-v4-hibernate

Thanks

[smaelc]

The issue still, org.opentest4j.AssertionFailedError: Unexpected exception thrown: org.springframework.dao.DataIntegrityViolationException: could not execute statement [ERROR: null value in column "created_by" of relation

[mp911de]

Thanks for getting in touch, but it feels like this question would be better suited to StackOverflow. As mentioned in the guidelines for contributing, we prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug.