Home server database about gourmet HOT 11 CLOSED

Submitted by SourceForge user rocketman768 on 2012-08-05 17:00:51 UTC.

+1 schappenberg. Just make a GUI option for the location of recipes.db. For syncing, I just made a symbolic link from ~/.gourmet/recipes.db to my Dropbox folder.

from gourmet.

Submitted by SourceForge user enfant_terrible on 2012-02-05 01:27:20 UTC.

Good to hear about posgres working!

As the Windows part is off-topic, please refer to this forum thread I've just created:
https://sourceforge.net/projects/grecipe-manager/forums/forum/371767/topic/4998743

from gourmet.

Submitted by SourceForge user indymaynard on 2012-02-04 23:26:52 UTC.

Well, after installing python-psycopg2, it seems to work fine. I did run into a problem with the nutritional values, but after closing and restarting, it seemed to work. However, I would love to know if anyone could tell me:

1. How to run gourmet 0.15.9 in Windows
2. How to build gourmet 0.15.9 in Windows

from gourmet.

Submitted by SourceForge user indymaynard on 2012-02-04 22:27:19 UTC.

I can tell you that MySQL didn't work even after the manual database alteration.

The error returned after that was:

sqlalchemy.exc.InvalidRequestError: VARCHAR requires a length when rendered on MySQL

Fedora always forgets my postgres stuff, so I have to reconfigure before I try. I really want to get this working...

from gourmet.

Submitted by SourceForge user enfant_terrible on 2012-02-04 21:57:59 UTC.

I haven't tried postgres yet. If you do, please comment here on the result!

from gourmet.

Submitted by SourceForge user indymaynard on 2012-02-04 21:36:34 UTC.

When you say "some backends," does that include postgres? I have yet to try that.

from gourmet.

Submitted by SourceForge user enfant_terrible on 2012-01-30 19:02:32 UTC.

I've also tried it out. The problem is that some backends (like MySQL) are "pickier" than others (like SQLite).
To make this work, I will need to change the database layout a bit, which will also require some tweaks in order to ensure backwards compatibility.

If you don't want to wait, you might want to try to modify the database layout manually, as described in this blog post:
http://blog.henrygis.com/2011/02/setting-up-gourmet-recipe-manager-part.html

from gourmet.

Submitted by SourceForge user indymaynard on 2012-01-30 03:27:21 UTC.

Sadly, the suggested --database-url command does not work. In my particular case, that gives me this error:

sqlalchemy.exc.OperationalError: (OperationalError) (1170, "BLOB/TEXT column 'ingkey' used in key specification without a key length") '\nCREATE TABLE shopcats (\n\tingkey TEXT NOT NULL, \n\tshopcategory TEXT, \n\tposition INTEGER, \n\tPRIMARY KEY (ingkey)\n)\n\n' ()

I am not a python programmer, nor do I suspect that I will learn it anytime soon, but I messed with the source code a little a year or so back. Whenever I "fixed" one problem, another popped up. It seems as though SQLAlchemy doesn't make it as seamless as I thought it would.

I would love this feature! I have a whole family that is interested in this!

from gourmet.

Submitted by SourceForge user enfant_terrible on 2012-01-15 17:29:27 UTC.

@schappenberg: you can already change the location of recipes.db, using the --gourmetdir command line option.
use gourmet --help to see all possible options.

as for server-based database storage, gourmet uses SQLAlchemy -- by default to access a SQLite database, but using the --database-url command line option, you might also succeed using e.g. a MySQL db instead.

from gourmet.

Submitted by SourceForge user schappenberg on 2011-12-30 04:57:04 UTC.

i'll give that a +1
As a suggestion, just add an option to change the location of the recipes.db. So i also would have the possibility to manage more recipes.db's e.g. for more than one gourmet users on one PC or to manage soups in a different Database than grilling recipes.

from gourmet.

Splitting this issue into #681 and #682, closing.

from gourmet.