It is possible that I did in this manner before, because now everything
works fine on the remote connection.
Also transactions works with JPA, but no in SQL as you said.
Thank you for your help
Tomek
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB"
do you connect to server or local file if you connect to local file you
have 2 different istances of dbs so you need to reload data.
On Wed, Sep 10, 2014 at 10:48 AM, Tomasz Kułakow
wrote:
>
> Sorry which changes ?
>>
>
>
> I have in the console:
> orientdb {db}> select from #12:0
>
> +-
> Sorry which changes ?
>
I have in the console:
orientdb {db}> select from #12:0
+-++---
# |@RID |@version|value
+-++---
0 |#12:0|21 |22
+-++---
then with still active console I run the Java program, which change 'val
Sorry which changes ?
On Wed, Sep 10, 2014 at 8:57 AM, Tomasz Kułakow
wrote:
> Thanks for your response,
> I'll use plocal then.
> And why changes are not visible in the console immediately? I can see
> them after restarting the console.
>
>> --
>
> ---
> You received this message because you
Thanks for your response,
I'll use plocal then.
And why changes are not visible in the console immediately? I can see them
after restarting the console.
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and s
Hi Tomek,
Currently in remote connection SQL commands are not running under
transaction, so you should use Java API to perform document changes.
For sure we are going to fix this issue in next releases.
On Tue, Sep 9, 2014 at 4:25 PM, Tomasz Kułakow
wrote:
> 1) Why transactions don't work when
1) Why transactions don't work when remote connection is in use? Tutorial
says its READ COMMITTED, so it should work.
2) How to check in console if something has changed in the database after
program execution?
In console i checked
orientdb {db}> select from #12:0
+-++---
#
