gallery3 and other db types
|
kovert
Joined: 2007-04-16
Posts: 4 |
Posted: Thu, 2009-07-30 03:54
|
|
I know postgresql (or other db) support is not slated for gallery 3 because its not in the "stuff most users use" category. I have a few gallery2 installations that are against postgresql and I'm contemplating my gallery3 options. I'm not sure if the upgrade allows you to go from pg to mysql (I doubt it, but I don't yet have a working mysql install), and I'm disinclined to run mysql just for one app. What I was wondering is that if a patch that added postgresql (and possibly oracle if I have time) support that was well tested to make sure it was supported for mysql would be accepted and there's any interest in trying to ensure that it worked in future releases. Messing around, I was able to get the database to load up properly in pgsql, but got stopped by the extensive use of the non-ansi ` to quote column names throughout the gallery core. In order to support additional databases, double quotes would need to be used (either that, or column names that did not need to be quoted). This seemed like a big enough change that it may not be interesting to the gallery 3 developers, but its also prevelent enough that maintaining my own person mini-patch with support of pgsql is just not feasible. I have only spent a preliminary amount of time looking into this, so I'm not sure what else might be involved. thoughts? thanks, |
|
Posts: 25
If you follow the mailing list there is a guy on there who is pushing the pg path. He's offered a few patches to the team (which have been accepted) and seems to know his stuff.
I think with this you can be pretty confident that even though it wont be supported, you will have g3 working on pg database.
Posts: 27300
Here is his relevant thread(s) the the devel list:
http://www.nabble.com/user/UserPosts.jtp?user=1518426
also his git repository:
http://github.com/rledisez
Dave
_____________________________________________
Blog & G2 || floridave - Gallery Team
Posts: 4
Thanks very much for the the pointer.
In reading the thread, since gallery3 is continuing to do non-ANSI things like back quotes instead of double quotes to use reserved words, the degree of work required to make things work with postgresql seems like it could be a problem, particulary if the other guy decides to stop working on it. I'm sure I can keep it up if I put enough effort into it, but its not clear if its worth it.
For those of us that have gallery2 running with something else, is there some process for getting to mysql for gallery3 from that something else? Googling found some rather onerous processes for converting gallery2 from one to the other, but I was hoping there might be something more straightforward. Apologies if I missed a thread in the forums; I didn't find anything, but could just be not combing the right words.
thanks,
-Todd
Posts: 4
heh. I'm apparently an idiot and should read the rest of the threads you pointed me to; looks like some of that stuff is changing after all.
Having said that, is there a process for moving from one to the other, or does that fall into the "not enough users" category?
thanks muchly,
-Todd
Posts: 16504
Moving from one DB to another? Yes, "not enough users"
Even fewer than those wanting something else than MySQL. I don't believe there was anything supported like that in G2 and I doubt there will be anything like that for G3. It would take those interested in PG or any other DB to write something for that conversion.
Oh wait, I just read your other post. If you want to run MySQL for G3, I think it would be a simple matter of installing and setting up MySQL on the same server your G2 is running with PG. G3 doesn't interact directly with the database to import your G2 install, it uses G2's API. So in theory it should be just like anyone else migrating from G2 to G3. Just have them both running on the same server and use the G2 Import module in G3 to import your G2 data.
____________________________________________
Like Gallery? Like the support? Donate now!!! See G2 live here