|
From: klavs k. <kl...@vs...> - 2002-03-07 15:35:34
|
Hi everybody, I'm new to sql-ledger - I got pointed to it by my local LUG (www.sslug.dk). I can see it only supports postgres, which is very unfortunate for me, as my only server only has 64mb's of ram, and I'm running mysql (which I use for my PHP) and a lot of other stuff on it already. This is my reasoning for not wanting to embark on postgres ( please no flames :-). I found some links describing that it was "only" a specific type of SQl statements that didn't work in MySQL and that it also had something to do with MySQL's lack of transaction support. With the links I found, I could ofcourse just exchange the sql statements as described and my version would probably be up and running.. but I would very much like for whatever change, to be in the main code, so that I wouldn't have to do the whole thing over again when 1.8.3 emerges, and so on. Do you have any plans for example, for making SQL-ledger workable with both databases.. seeing as how MySQL's Innodb gives it transactions support, there shouldn't be an immediate problem, or? well anyways, I'm very interested in your work with the sql-ledger and hope to be able to use it, one way or the other. Thank you in advance. --=20 Regards, Klavs Klavsen -------------| This mail has been sent to you by: |------------ Klavs Klavsen - Open Source Consultant=20 kl...@vs... - http://www.vsen.dk Get PGP key from www.keyserver.net - Key ID: 0x586D5BCA=20 Fingerprint =3D A95E B57B 3CE0 9131 9D15 94DA E1CD 641E 586D 5BCA --------------------[ I believe that... ]----------------------- It is a myth that people resist change. People resist what other people make them do, not what they themselves choose to do... That's why companies that innovate successfully year after year seek their peopl's ideas, let them initiate new projects and encourage more experiments. -- Rosabeth Moss Kanter |
|
From: Sergio A. K. <ser...@ho...> - 2002-03-07 18:41:13
|
----- Original Message ----- From: "klavs klavsen" <kl...@vs...> > Hi everybody, > > I'm new to sql-ledger - I got pointed to it by my local LUG > (www.sslug.dk). > > I can see it only supports postgres, which is very unfortunate for me, > as my only server only has 64mb's of ram, and I'm running mysql (which I > use for my PHP) and a lot of other stuff on it already. This is my > reasoning for not wanting to embark on postgres ( please no flames :-). I'm running postgres on a 32mb machine, and it run well. > I found some links describing that it was "only" a specific type of SQl > statements that didn't work in MySQL and that it also had something to > do with MySQL's lack of transaction support. it's not only transaction support, is a lot of things... (UNIONs, subselects, JOIN, foreign keys, VIEWs, etc) > With the links I found, I could ofcourse just exchange the sql > statements as described and my version would probably be up and > running.. but I would very much like for whatever change, to be in the > main code, so that I wouldn't have to do the whole thing over again when > 1.8.3 emerges, and so on. look, we are talking about money here, you don't want to run it in a database that is not ACID compliant, trust me, you don't *really* want... running a storyboard with mysql is fine, running a system that manage money is another thing altogheter... hey, what's the problem of learning postgresql ? (for me pgsql was easier to learn than mysql, and I aproached pgsql after mysql) this book is good for begginers: http://www.postgresql.org/docs/aw_pgsql_book/index.html /sergio |
|
From: kevin b. <kev...@bi...> - 2002-03-07 21:47:24
|
hi klavs, i know its not the answer you want - but databases have a habit of growing - and 4 or 5 years down the line when you are responsible for possibly dozens of companies accounts you will be glad you chose an ACID compliant DB such as postgres, kev Sergio A. Kessler wrote: > ----- Original Message ----- > From: "klavs klavsen" <kl...@vs...> > >>Hi everybody, >> >>I'm new to sql-ledger - I got pointed to it by my local LUG >>(www.sslug.dk). >> >>I can see it only supports postgres, which is very unfortunate for me, >>as my only server only has 64mb's of ram, and I'm running mysql (which I >>use for my PHP) and a lot of other stuff on it already. This is my >>reasoning for not wanting to embark on postgres ( please no flames :-). >> > > I'm running postgres on a 32mb machine, and it run well. > > >>I found some links describing that it was "only" a specific type of SQl >>statements that didn't work in MySQL and that it also had something to >>do with MySQL's lack of transaction support. >> > > it's not only transaction support, is a lot of things... > (UNIONs, subselects, JOIN, foreign keys, VIEWs, etc) > > >>With the links I found, I could ofcourse just exchange the sql >>statements as described and my version would probably be up and >>running.. but I would very much like for whatever change, to be in the >>main code, so that I wouldn't have to do the whole thing over again when >>1.8.3 emerges, and so on. >> > > look, we are talking about money here, you don't want to run > it in a database that is not ACID compliant, trust me, you don't > *really* want... > running a storyboard with mysql is fine, running a system that > manage money is another thing altogheter... > > hey, what's the problem of learning postgresql ? > (for me pgsql was easier to learn than mysql, > and I aproached pgsql after mysql) > > this book is good for begginers: > http://www.postgresql.org/docs/aw_pgsql_book/index.html > > /sergio > > > > |
|
From: Kenneth G. <la...@th...> - 2002-03-08 02:20:42
|
i have 64 mb ram and am running both mysql and postgres on my machine and a lot of other stuff - mail server, dial in server, web server, kde, games etc etc. no problems kg On Thursday 07 March 2002 21:05, klavs klavsen wrote: > Hi everybody, > > I'm new to sql-ledger - I got pointed to it by my local LUG > (www.sslug.dk). > > I can see it only supports postgres, which is very unfortunate for me, > as my only server only has 64mb's of ram, and I'm running mysql (which I > use for my PHP) and a lot of other stuff on it already. This is my > reasoning for not wanting to embark on postgres ( please no flames :-). > ---------------------------------------- |