*** dcmwai has quit IRC *** holycow has quit IRC *** johannesV has joined #gnuenterprise *** nickr has quit IRC *** nickr has joined #gnuenterprise *** reinhard has joined #gnuenterprise *** kilo has joined #gnuenterprise *** Amorphous has joined #gnuenterprise *** kilo has quit IRC reinhard: are you there ? *** Amorphous has left #gnuenterprise yes for about 5 minutes or so ah, ok meanwhile i think i've traced the bug into pySQLite module seems as if the 'autocommit'-option is not properly implemented; using a sqlite datasource with forms work well, but using it with appserver in between results in a 'database locked' after reading tons of code lines (and adding debug-output as well) the situation seems to be as follows: two processes connecting to the same db (file) both creating a cursor process a executes a query on this cursor (-> implicit start of transaction) process b executes a query and fails (database locked) even if the query is just a normal select if processes send an explicit commit after executing the query it works oh so it's not really multi user enabled? so sqlite-module defines a connect-parameter called 'autocommit' but looking at the implementation it behaves strange on the execute it does NOT start a transaction before the execute, and in the commit-function it raises an execption so it's not possible to use transactions at all ?! well it's sort of multiuser capable (as written in the doc); the point is, there might be no simultaneous transactions running on the same file aha file == table? no, file == multiple tables one file is a db, holding as much tables as you like ah ok hmm might be a problem with the 2 session we have with appserver i've solved this problem (with a fix as i think) the internal session (for the classrep) and the user session ok great a fix in our code or a fix in sqlite code? why did the connection-manager uses an own instance of GConnections and the geasSession uses another one fix in appserver-code while geasSession get's a GConnections instance by param ? this means, geasSession does NOT reuse already opened connections yes that's right we want sepearte connections for each session because databases do commits on connection level so every session has to open its own connection ah, ok, so i'll remove this 'fix' good, this means sqlite is not usable with appserver at all if i set autocommit to 'true' all queries work well, and the first commit raises an execption: Commit failed - autocommit is on. ok i think i get the point sqlite doesn't support multiple parallel transactions right setting autocommit means 'turn off transactions' so we won't be able to use sqlite with appserver *until* we implement transactions on appserver level ok have to leave now l8r *** reinhard has quit IRC *** johannesV_ has joined #gnuenterprise *** johannesV has quit IRC *** jcater has joined #gnuenterprise *** stan has left #gnuenterprise *** havoc has quit IRC *** havoc has joined #gnuenterprise *** johannesV_ has quit IRC *** kreiszner has joined #gnuenterprise I have designer up and running but can't get it to connect to a postgres db. The db has a test db with test as the owner. Any suggestions? Designer seems to ignore changes to the /etc/gnue/connections.conf file. are you running an installed version of gnue? or from svn? actually, try this: rm -rf /usr/local/gnue/etc; ln -s /etc/gnue /usr/local/gnue/etc *** kreiszner has quit IRC *** dsmith has joined #gnuenterprise *** sjc has joined #gnuenterprise *** kilo has joined #gnuenterprise *** kilo has quit IRC *** bluesbaron_ has joined #gnuenterprise *** bluesbaron_ has left #gnuenterprise *** dsmith has quit IRC *** jcater has quit IRC