Postgresql compatiblity for webhomer and contribution flow

[Jonathan Liuti]

Hi there,

For one of the project I'm currently working on I'm aiming towards compatibility with postgresql to simplify our architecture and remove the mysql dependency.

Is anybody working on such a thing yet ?

So far so good I was able to get webhomer running, database schema instantiated, but I'm facing some issues with sql queries which I'm in the process of fixing.

That leads me to those questions:

• Do you have any kind of automated build system for the project with tests and stuff ?
• What is the recommended way of submitting code ? And starting a review ?

PS: Any reason why you are not using Github ? Contributing is far more simple via pull request than here, just my 2 cents.

Cheers

[Lorenzo Mangani]

Hi Jonathan,

HOMER will move to Github soon with its next major - we have not done it so far just for organizational challenges but its upcoming to facilitate everyone's life.

We have quite a lot of users with HOMER using PGSQL, what challenges are you trying to solve/enhance exactly at this time?

As of the questions: 

- Most legwork in HOMER is done inside Kamailio by our sipcapture module, and we trust their build systems - the remainder is just UI/configs which are validated per release.

- You can submit a patch to our issue tracker and/or request commit access to the repository (this will change once proj. moves to GitHub)

All the best,

Lorenzo Mangani

HOMER / PCAPTURE DEV TEAM

Desk: +31 20 8080468 / +1 202-632-7227

Mobile: +31 6 4603-2730

QXIP BV - Capture Engineering

Amsterdam, The Netherlands

g...@pcapture.com

--
You received this message because you are subscribed to the Google Groups "Homer Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to homer-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jonathan Liuti]

Hi Lorenzo,

I'm having some issues with sql queries that are only mysql compatible. So far I spotted:

1. doing a `select database_name.field_name from X;` is not valid in postgresql
2. GROUP BY clause referencing only one field when multiple fields are used in the SELECT is also not valid.
   

This is mainly happening in the dashboard and on search queries.

I already fixed the first issue and I'm looking at converting the search queries using group by clauses and this is a by far more complex ;-)

Awesome news regarding github ! Any ETA on this ? Not trying to push you, just wondering if I should wait before submitting code as it will, indeed, make my life easier :-)

Also, I spent quite some time looking at your code base and I feel, but thats really only my opinionated view as a django / python dev, that you would greatly benefit from switching from php to python... But I guess I'm surely not the first one to claim that.

Anyway, for now the scope of my doing is only to get the project up and running in postgresql, if you have any pointer that could help speed up the process I'd be more than pleased to hear them ;-)

Cheers,

John.

[Lorenzo Mangani]

John,

Thanks for the clarifications - and for picking up this task for contribution. I would kindly ask and suggest sending the patches to us or committing on googlecode as the switch will most likely happen towards the very beginning of 2015. As of the UI and php code, we've been working on a new client-side full interface which will not require as much from the backend (other than to handle API calls) so much of the currently "aging" code is to be replaced by something much more streamlined in the near future, opening the way for a language migration if convenient. When the time comes, most of the core queries should remain in place within the API, so any work on the pgsql front should remain valid and live on.

If you can use any support, the list and the developers are all tuned here.

Best Regards,

Lorenzo Mangani

HOMER / PCAPTURE DEV TEAM

Desk: +31 20 8080468 / +1 202-632-7227

Mobile: +31 6 4603-2730

QXIP BV - Capture Engineering

Amsterdam, The Netherlands

g...@pcapture.com

[Jonathan Liuti]

Do you happen to have any requirements for the rest api ?

I have been building rest api's a lot in the last years, maybe I could give you some input.

I'm also wondering what would be the load of work to get this api migrated to django, especially if you plan on relying on a big fat javascript client.

If you aim to offer multi database backends support, switching to an ORM will definitely ease the pain.

It's probably not worth it to try to achieve this on your own, lot of edge cases...

Anyway, good to hear that the project is well alive and heading in great direction.

Bests,

John.