Updates...

classic Classic list List threaded Threaded
11 messages Options
Stéphane Gauvin Stéphane Gauvin
Reply | Threaded
Open this post in threaded view
|

Updates...

Hello Friend,

How can I get the "trunk" up to date version of pERP ?

Thanks,

Snoopyski
Nathan Gray-2 Nathan Gray-2
Reply | Threaded
Open this post in threaded view
|

Re: Updates...


On 13-Sep-07, at 6:46 AM, Snoopyski wrote:

>
> Hello Friend,
>
> How can I get the "trunk" up to date version of pERP ?

  svn co https://perp.svn.sourceforge.net/svnroot/perp/trunk perp


Nathan Gray
nathan at goarctic dot com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Nathan Gray-2 Nathan Gray-2
Reply | Threaded
Open this post in threaded view
|

Re: Updates...

In reply to this post by Stéphane Gauvin

On 13-Sep-07, at 6:46 AM, Snoopyski wrote:

>
> Hello Friend,
>
> How can I get the "trunk" up to date version of pERP ?

Also of interest is:
http://www.projecterp.org/mediawiki/index.php/Site_Installation

Nathan Gray
nathan at goarctic dot com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Michael Zoet-2 Michael Zoet-2
Reply | Threaded
Open this post in threaded view
|

New to perp and the mailinglist

Hi to all,

I'm new to perp and the perp devel mailinglist, so I wanted to say hello
:-).

I just installed perp from the SVN sources and everything seems to run
fine, except:

I'm using PostgreSQL as my database backend. As I have read in the mail
archives this is a known problem. And there are some patches around to
fix this. Am I right? Is there the possiblity getting these patches?

I really like to get perp running with PostgreSQL DB and willing to test
this further. (I have several eGW with PostgreSQL installation up and
running for testing).

So now I'm trying to learn and setup perp, except for the ledger and
manufacturing applications.

Greetings,

Michael



Setup error description for perp_ledger and perp_manufacturing (the
other applications install without errors) as the eGW setup shows:

Anwendung installierenn/entfernen/aktualisieren:

CreateTableSQL('perp_account_group','group_name C(255), group_section
I4, group_id I4 NOTNULL PRIMARY, asset_or_liability I4 NOTNULL NOQUOTE
DEFAULT 1') sql=Array ( [0] => CREATE TABLE perp_account_group (
group_name VARCHAR(255), group_section INT4, group_id INT4 NOT NULL,
asset_or_liability INT4 DEFAULT 1 NOT NULL, PRIMARY KEY (group_id) ) )

*ERROR: relation "perp_account_group" already exists*

CreateIndexSql('perp_account_group_name','perp_account_group','group_name',Array
( [0] => UNIQUE ) ) sql=Array ( [0] => CREATE UNIQUE INDEX
perp_account_group_name ON perp_account_group (group_name) )

*ERROR: "perp_account_group" is an index*

CreateIndexSql('perp_account_group_section','perp_account_group','group_section',False)
sql=Array ( [0] => CREATE INDEX perp_account_group_section ON
perp_account_group (group_section) )

*ERROR: "perp_account_group" is an index*


perp_ledger Tabellen wurden installiert, außer oben sind Fehlermelungen
zu sehen.

CreateTableSQL('perp_build_option_category','build_option_category_id I
AUTOINCREMENT NOTNULL PRIMARY, build_option_category_name C(50) NOTNULL,
stock_category I4 NOTNULL, required L NOTNULL NOQUOTE DEFAULT true')
sql=Array ( [0] => CREATE TABLE perp_build_option_category (
build_option_category_id SERIAL, build_option_category_name VARCHAR(50)
NOT NULL, stock_category INT4 NOT NULL, required BOOLEAN DEFAULT true
NOT NULL, PRIMARY KEY (build_option_category_id) ) )

*ERROR: relation "perp_build_option_category" already exists*

CreateIndexSql('perp_build_option_category_name','perp_build_option_category','build_option_category_name',Array
( [0] => UNIQUE ) ) sql=Array ( [0] => CREATE UNIQUE INDEX
perp_build_option_category_name ON perp_build_option_category
(build_option_category_name) )

*ERROR: "perp_build_option_category" is an index*

CreateIndexSql('perp_build_option_category_stock_category','perp_build_option_category','stock_category',False)
sql=Array ( [0] => CREATE INDEX
perp_build_option_category_stock_category ON perp_build_option_category
(stock_category) )

*ERROR: "perp_build_option_category" is an index*


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Nathan Gray-2 Nathan Gray-2
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL


On 15-Sep-07, at 4:47 AM, Michael Zoet wrote:

> Hi to all,
>
> I'm new to perp and the perp devel mailinglist, so I wanted to say  
> hello
> :-).

Hello, and welcome.

> I just installed perp from the SVN sources and everything seems to run
> fine, except:
>
> I'm using PostgreSQL as my database backend. As I have read in the  
> mail
> archives this is a known problem. And there are some patches around to
> fix this. Am I right? Is there the possiblity getting these patches?

The patches are incomplete, they're only for perp_ar I think.  They  
were submitted a while ago by Camilo Alejandro Arboleda, but I had  
some questions he didn't answer, so I didn't implement all of his  
changes.
http://sourceforge.net/tracker/index.php?
func=detail&aid=1695071&group_id=166007&atid=837656

> I really like to get perp running with PostgreSQL DB and willing to  
> test
> this further. (I have several eGW with PostgreSQL installation up and
> running for testing).

I don't have a postgreSQL server to test against, and don't have time  
to test against it, but if you've got the time, I would be happy to  
apply your patches as you get each application working.  You may want  
to have a MySQL installation for comparison, so you know what works  
and what doesn't.

> So now I'm trying to learn and setup perp, except for the ledger and
> manufacturing applications.

Nope, sorry.  You need the ledger before any of the others will work,  
as they use the general ledger.  It's not much of an accounting  
system otherwise.
You can do without the manufacturing, if you don't need it, but you  
need the ledger.  (The reason it's not forced in the dependencies is  
because it's annoying for us developers).


> Setup error description for perp_ledger and perp_manufacturing (the
> other applications install without errors) as the eGW setup shows:
>
> Anwendung installierenn/entfernen/aktualisieren:
>
> CreateTableSQL('perp_account_group','group_name C(255), group_section
> I4, group_id I4 NOTNULL PRIMARY, asset_or_liability I4 NOTNULL NOQUOTE
> DEFAULT 1') sql=Array ( [0] => CREATE TABLE perp_account_group (
> group_name VARCHAR(255), group_section INT4, group_id INT4 NOT NULL,
> asset_or_liability INT4 DEFAULT 1 NOT NULL, PRIMARY KEY (group_id) ) )
>
> *ERROR: relation "perp_account_group" already exists*
>
> CreateIndexSql
> ('perp_account_group_name','perp_account_group','group_name',Array
> ( [0] => UNIQUE ) ) sql=Array ( [0] => CREATE UNIQUE INDEX
> perp_account_group_name ON perp_account_group (group_name) )
>
> *ERROR: "perp_account_group" is an index*
>
> CreateIndexSql
> ('perp_account_group_section','perp_account_group','group_section',Fal
> se)
> sql=Array ( [0] => CREATE INDEX perp_account_group_section ON
> perp_account_group (group_section) )
>
> *ERROR: "perp_account_group" is an index*

Looks like this table is already created somewhere aready?  It may  
work anyway, but if you can figure out what causes it, I'll happily  
fix it for you.


> perp_ledger Tabellen wurden installiert, außer oben sind  
> Fehlermelungen
> zu sehen.
>
> CreateTableSQL
> ('perp_build_option_category','build_option_category_id I
> AUTOINCREMENT NOTNULL PRIMARY, build_option_category_name C(50)  
> NOTNULL,
> stock_category I4 NOTNULL, required L NOTNULL NOQUOTE DEFAULT true')
> sql=Array ( [0] => CREATE TABLE perp_build_option_category (
> build_option_category_id SERIAL, build_option_category_name VARCHAR
> (50)
> NOT NULL, stock_category INT4 NOT NULL, required BOOLEAN DEFAULT true
> NOT NULL, PRIMARY KEY (build_option_category_id) ) )
>
> *ERROR: relation "perp_build_option_category" already exists*
>
> CreateIndexSql
> ('perp_build_option_category_name','perp_build_option_category','build
> _option_category_name',Array
> ( [0] => UNIQUE ) ) sql=Array ( [0] => CREATE UNIQUE INDEX
> perp_build_option_category_name ON perp_build_option_category
> (build_option_category_name) )
>
> *ERROR: "perp_build_option_category" is an index*
>
> CreateIndexSql
> ('perp_build_option_category_stock_category','perp_build_option_catego
> ry','stock_category',False)
> sql=Array ( [0] => CREATE INDEX
> perp_build_option_category_stock_category ON  
> perp_build_option_category
> (stock_category) )
>
> *ERROR: "perp_build_option_category" is an index*

Same with this one?
While I have used PostgreSQL, I really can't say.

Nathan Gray
nathan at goarctic dot com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Michael Zoet-2 Michael Zoet-2
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL

Hi Nathan,


>
> ...
>
> The patches are incomplete, they're only for perp_ar I think.  They
> were submitted a while ago by Camilo Alejandro Arboleda, but I had
> some questions he didn't answer, so I didn't implement all of his
> changes.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1695071&group_id=166007&atid=837656
>
>
I will take a look into it. But it will take time as I'm not an SQL
master. First I have to setup eGW with MySQL to get a working pERP ;-).
Then I will apply the diff to the current SVN HEAD version of pERP and
see if it gets better or worse wth Postgres. Is it ok to use the SVN
HEAD version?

>> I really like to get perp running with PostgreSQL DB and willing to test
>> this further. (I have several eGW with PostgreSQL installation up and
>> running for testing).
>
> I don't have a postgreSQL server to test against, and don't have time
> to test against it, but if you've got the time, I would be happy to
> apply your patches as you get each application working.  You may want
> to have a MySQL installation for comparison, so you know what works
> and what doesn't.
I will try to do this.

>
>> So now I'm trying to learn and setup perp, except for the ledger and
>> manufacturing applications.
>
> Nope, sorry.  You need the ledger before any of the others will work,
> as they use the general ledger.  It's not much of an accounting system
> otherwise.
> You can do without the manufacturing, if you don't need it, but you
> need the ledger.  (The reason it's not forced in the dependencies is
> because it's annoying for us developers).
Yes, I have already seen this...

I hope to come up with something in 2 weeks.


Michael

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Nathan Gray-2 Nathan Gray-2
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL


On 18-Sep-07, at 2:15 AM, Michael Zoet wrote:

> I will take a look into it. But it will take time as I'm not an SQL
> master. First I have to setup eGW with MySQL to get a working  
> pERP ;-).
> Then I will apply the diff to the current SVN HEAD version of pERP and
> see if it gets better or worse wth Postgres. Is it ok to use the SVN
> HEAD version?

Yes, that would be the best way to go about it.  Be careful though, I  
don't know if the patch will even apply anymore, because so much has  
changed since then.

> ...
> I hope to come up with something in 2 weeks.

Feel free to ask any questions you need as you go, and if you find  
things that are just wrong regardless of which database is used, let  
me know and I'll fix them right away.
Good luck.

Nathan Gray
nathan at goarctic dot com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Michael Zoet-2 Michael Zoet-2
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL

Hi Nathan and all others,

for now I had no time to work on pERP and PostgreSQL.
Tomorrow I'm going on a one week holiday. White water kayaking in the
european alpes.

After that I have new energy and hopefully the time.

Michael

>
> On 18-Sep-07, at 2:15 AM, Michael Zoet wrote:
>
>> I will take a look into it. But it will take time as I'm not an SQL
>> master. First I have to setup eGW with MySQL to get a working pERP ;-).
>> Then I will apply the diff to the current SVN HEAD version of pERP and
>> see if it gets better or worse wth Postgres. Is it ok to use the SVN
>> HEAD version?
>
> Yes, that would be the best way to go about it.  Be careful though, I
> don't know if the patch will even apply anymore, because so much has
> changed since then.
>
>> ...
>> I hope to come up with something in 2 weeks.
>
> Feel free to ask any questions you need as you go, and if you find
> things that are just wrong regardless of which database is used, let
> me know and I'll fix them right away.
> Good luck.
>
> Nathan Gray
> nathan at goarctic dot com
>
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
Nathan Gray-2 Nathan Gray-2
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL


On 29-Sep-07, at 6:04 AM, Michael Zoet wrote:

> Hi Nathan and all others,
>
> for now I had no time to work on pERP and PostgreSQL.
> Tomorrow I'm going on a one week holiday. White water kayaking in the
> european alpes.

Nice!  I could go for some of that...


Nathan Gray
nathan at goarctic dot com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers
guillaume vidon guillaume vidon
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL

In reply to this post by Michael Zoet-2
Hi, it s a old topic but the problem is still here.
I try to create manually the table  perp_account_group and i found what is the problem :
relation "perp_account_group" already exists
There are a conflict with the name of the account_name table index.

To resolve this, i have replaced      
'ix' => array('account_group'),
by
'ix' => array('account_group_ix'),
on perp_ledger/setup/tables_baseline.inc.php
I would like to know if I will have some pbs if i change the index of account_group. Seems not use.
Thxs
GV
Nathan Gray Nathan Gray
Reply | Threaded
Open this post in threaded view
|

Re: pERP + PostgreSQL

guillaume vidon wrote:

> Hi, it s a old topic but the problem is still here.
> I try to create manually the table  perp_account_group and i found what is
> the problem :
> relation "perp_account_group" already exists
> There are a conflict with the name of the account_name table index.
>
> To resolve this, i have replaced      
> 'ix' => array('account_group'),
> by
> 'ix' => array('account_group_ix'),
> on perp_ledger/setup/tables_baseline.inc.php
> I would like to know if I will have some pbs if i change the index of
> account_group. Seems not use.
>  

I don't think this will cause you problems, but I'm not familiar with
the format of those files.  I'm under the impression that the line in
question defines an index on the account_group column.  If this is true,
I don't know what your change will do.  If it works, you should probably
change it in tables_current.inc.php too, and send me the changes so I
can commit them.

Note that postgres will have many more problems than this, particularly
with some of the GROUP BY and ORDER BY clauses.  It's not that I have
anything against postgres, just not enough time to figure out the
differences and work through them.

Nathan

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Perp-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/perp-developers