anna_a <[email protected]> writes: > has data type decimal and precision 3. If i for example want to change a > value from 1 to 0.5 I type in 0.5 and then press the "commit > record(s)"button. So far so good, it looks like everything's been saved like
Anna, it seems as if you are seeing this from an application or IDE, since Derby doesn't have GUI buttons. I think you will need to provide some more information before we can help you. Derby does allow you to trace the SQL being executed, though, cf. http://db.apache.org/derby/docs/10.5/ref/rrefproper43517.html Dag > i wanted it to. Now to the problem: if I choose to insert a new record the > decimal value I'd entered disappears and is replaced with the previous > integer (1 in this case). This only happens if i've updated the table by > entering a new decimal value, not if the new correlation is an integer like > 0 for example. Does anyone know what i'm doing wrong? > > > > Kind regards, > > Anna > -- > View this message in context: > http://www.nabble.com/problem%3A-column-values-in-database-are-not-saved-tp25129010p25129010.html > Sent from the Apache Derby Users mailing list archive at Nabble.com. >
