[Perfparse-devel-int] Re: [Perfparse-devel] PostgreSQL Storage

[Ben C. <bcl...@pe...>]

Priewasser

Sorry for not replying sooner.

There will be a great deal of interest in your work.  I am sure there 
are many users who will want to use this version without delay.

Please beware of changed.  There are a few.  Look at the Change Log in 
each version.  Subscribe to the perfparse-devel-int mailing list, any 
changes should be posted there.  (This email is 'cc' to this list.)

Change so far:

- The function 'addField' now returns 'int'.  It used to return 'void'.

- On the host, service and metric tables I have added a second unique 
key, which will be used in later versions of code.  Called host_id, 
service_id and metric_id.  Change to code in storage_mysql to correctly 
populate this field.

If you want to share any information, please create a document on 
wiki.perfparse.org.  This can be used as a URL in any work you complete.

For the time being, please don't touch the 'summary' tables.  These are 
being changed at the moment.  I don't want you to waist any time!

Please let us know if there is anything you need from us, we are all 
here to help!

Regards,

Ben




Priewasser, Friedrich wrote:

> Hi,
> 
> Thanks for your quick response and for the tips. I will try to build the PostgreSQL storage the way you described (starting in about a week or two).
> At first sight I think there schould be no "big" problem converting the storage from MySQL to PostgreSQL.
> 
> Regards,
> Friedrich
> 
> 
> 
>>Priewasser,
>>
>>I have been talking to my partner Yves and we believe the best way to 
>>convert the product is as follows:
>>
>>
>>1.  Convert the database schema:
>>
>>	contrib/postgresql_create.sql
>>	contrib/postgresql_delete.sql
>>
>>Try to keep to ANSI-SQL.  Eg, use BOOL, TRUE and FALSE which MySQL does 
>>not support.  Rather than copying MySQL including it's short fallings :)
>>
>>This stage will give you a good idea of the challange to complete the work.
>>
>>
>>2.  Two bits of work here, storage module and DBMS library.
>>
>>(i) Copy modules/storage_mysql.* to modules/storage_postgresql.*
>>
>>Edit where required.  Keep the .h the same in all cases.
>>
>>(ii) Copy directory libpp_mysql to libpp_postgresql.
>>
>>Edit all parts, starting with dbms.c.  Please keep .h files the same.
>>
>>
>>3. The non-graph CGI code.
>>
>>In the CGI code, check the SQL commands and replace where needed using 
>>syntax similar to:
>>
>>#ifdef MYSQL
>>	"SELECT * WHERE boolean_field = 1"
>>#elseif POSTGRESQL
>>	"SELECT * WHERE boolean_field = TRUE"
>>#endif
>>
>>These definitions do not work yet.  If you continue this work, these 
>>will be added.
>>
>>
>>4.  The graph module.
>>
>>Yves is re-writing this to access many data sources.  At this stage 
>>probably best to wait until this work is a little more mature.  I will 
>>be writing a MYSQL module at this point, so we can do this together.
>>
>>
>>
>>A lot has been said in response to your original email in a short time. 
>> I hope we haven't confused you.  We are excited about what your work 
>>will do for our product!
>>
>>Please let us know your feelings and what you think of the challange.
>>
>>Regards,
>>
>>Ben & Yves.
>>
> 
> 
> --
> Friedrich Priewasser
> Software Engineer
> Fabalabs Software GmbH
> Honauerstraße 4
> A-4020  Linz
> e-mail: mailto:fri...@fa...
> http://www.fabalabs.org
> 


-- 
Ben Clewett  bcl...@pe...
PerfParse    http://www.perfparse.org
PP FAQ       http://wiki.perfparse.org/tiki-list_faqs.php