https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
m

Muhammad Abdullah

11/24/2021, 7:03 AM
Hi All, I am using springboot and spring-data-jpa to create a rest-api that handles crud operations. I am using Postgresql as the DB. I can get it to work fine, however given the JSON example below I want to store the phoneNumbers, emails, addresses, urls, settings as JSON in the DB column for each one respectively. Is there a known way that this can be done? My data class is fairly simple: I have tried String, Map and Any as the data type for those fields none of which works.
@Table("organisations")
data class Organisation(
    @Id val id: UUID?,
    val name: String = "",
    val information: String = "",
    val urls: Any?,
    val emails: Any?,
    val phoneNumbers: Any?,
    val addresses: Any?,
    val settings: Any?,
    val active: Boolean = true,
    val createdAt: Instant = Instant.now(),
    val updatedAt: Instant = Instant.now(),
)
{ “name”: “Business Name”, “information”: “Business Info”, “phoneNumbers”: { “office”: “+6172345678”, “imam”: “+6142349876” }, “emails”: { “info”: “info@bus.com”, “commity”: “commity@bus.com” }, “addresses”: { “address”: “2345 SomeStreet Road, MyTOWN, 1234", “postal address”: “PO Box 123" }, “urls”: {}, “settings”: { “timeFormat”: “dd/MM/yyyy”, “currency”: “AUD” } } Any pointers or help would be greatly appreciated. Thanks
t

Ties

11/24/2021, 8:27 AM
Well, json is just a string, so I imagine that should work. Why didnt that work for you?
m

Muhammad Abdullah

11/24/2021, 9:26 AM
Thanks for the response. I get the following error when the request is deserialized: Resolved [org.springframework.http.converter.HttpMessageNotReadableException: JSON parse error: Cannot deserialize value of type
java.lang.String
from Object value (token
JsonToken.START_OBJECT
); nested exception is com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize value of type
java.lang.String
from Object value (token
JsonToken.START_OBJECT
) at [Source: (PushbackInputStream); line: 4, column: 21] (through reference chain: com.masjidlink.api.Organisation[“phoneNumbers”])]
My controller method that processes the request is:
@PostMapping
fun createNewOrganisation(@RequestBody newOrganisation: Organisation): ResponseEntity<Organisation> =
    ResponseEntity<Organisation>(service.saveOrganisation(newOrganisation), HttpStatus.OK)
So, it appears that the parts that I want to be stored as JSON strings are being translated to objects even though the field definition is a String.
t

Ties

11/24/2021, 9:35 AM
ah ok 🙂 I think I see what is happening here. Basicalliy what is going on is that you use the same object for a database entity and as a json object. This can sometimes indeed cause issues (on multiple fronts, even security).
As a start i would suggest making a seperate object that's being used in the API and one thats being used for the database. This gives you a lot more control over the exact types everywhere (because that is what your current problem is, if you find it interesting i can go into more details about that, but i think by making it 2 separate classes your problem will already fix itself, or at least makes it easy to fix it yourself)
m

Muhammad Abdullah

11/24/2021, 9:39 AM
So basically a DTO that contains for example a list of address objects and then I translate that to the format I want for the data class?
t

Ties

11/24/2021, 9:41 AM
you should make a OrganisationAPI class and a OrganisationEntity class (both can be data classes) and use the api class in the @RequestBody and use the @Table on the OrganisationEntity class
now you will have to do some manual mapping between the 2, but you can specify the exact types you want to use in both classes, for example, emails can be a string in the Entity class, but be a JSONObject in the API class (and you will have to map it from one type to another when storing or retrieving it)
m

Muhammad Abdullah

11/24/2021, 9:43 AM
I understand. That makes sense. Thanks for the help. I was trying to avoid duplicating code but I guess sometimes you can’t.
t

Ties

11/24/2021, 9:45 AM
In this case I basically always have different classes for API and entity, yes it may sound as duplication at first, but in practice there are a lot of reasons why you want to have separate classes for this; Sometimes (quite often) you do not want the same information (for example you might not want to expose the password field in a user object), sometimes the types don't match up (like you are experiencing), you dont always want to change the service API everytime you have a database change (or vice-versa) for backwards compatibility etc... so in practice in most cases it is good to have 2 classes for this, even if it means a bit of duplication
👍 2
m

Muhammad Abdullah

11/24/2021, 9:47 AM
Thanks for the help. That makes perfect sense.
t

Ties

11/24/2021, 9:47 AM
Happy to help 🙂
and let me know if you need any more background information 🙂
m

Muhammad Abdullah

11/24/2021, 9:49 AM
Much appreciated. I will.
ł

Łukasz Pięta

11/29/2021, 6:05 PM
Hi, you can also make a use of this repository -> https://github.com/vladmihalcea/hibernate-types With this dependency you can simply mark column as
jsonb
type (which is generally speaking
json
optimized for certain operations such as exctracting the value of object associated with some key) in your entity class.
@Entity
@TypeDef(name = "jsonb", typeClass = JsonBinaryType.class)
class Foo(
    @Id val id: UUID,
    @Type(type = "jsonb")
    @Column(columnDefinition = "jsonb")
    val bar: Bar
)
m

Muhammad Abdullah

02/05/2022, 10:06 AM
Thanks @Łukasz Pięta. Sorry, I missed this. I am trying to avoid using Hibernate.