After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 130879 - MySQL integration
MySQL integration
Status: RESOLVED OBSOLETE
Product: planner
Classification: Other
Component: Database
unspecified
Other All
: Normal enhancement
: ---
Assigned To: planner-maint
planner-maint
Depends on:
Blocks:
 
 
Reported: 2004-01-08 10:58 UTC by Bernhard Rohrer
Modified: 2021-06-09 20:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Schema from Lars Brandi Jensen (5.59 KB, text/plain)
2004-02-07 21:57 UTC, Richard Hult
Details

Description Bernhard Rohrer 2004-01-08 10:58:37 UTC
optionally use MySQL for storage - especially for multiuser access
Comment 1 Richard Hult 2004-01-08 11:02:18 UTC
There are plans for this, we just need someone to write a mysql scheme
and work with Alvaro to get the libgda move done. Are you interested
in helping out with this? You could join the development mailing list.
Comment 2 Bernhard Rohrer 2004-01-08 11:52:38 UTC
folks, I am a sysadmin, not a developer. I could maybe do the database 
design for you and that only by instinct and not scientifically. 
Coding is definitely not something I do. I am trying to help by making 
inane suggestions ;-)
Comment 3 Richard Hult 2004-01-08 12:03:48 UTC
:) If you have knowledge about the differences between postgresql and
mysql that would help, we just need to convert the postgresql scheme
to mysql.
Comment 4 Bernhard Rohrer 2004-01-08 12:06:12 UTC
sorry no :(
Comment 5 miles 2004-02-02 14:57:56 UTC
i can help with the mysql/postges schema/sql conversion, but moving to
libgda would be totally beyond me.  is that useful?
Comment 6 Richard Hult 2004-02-02 16:05:21 UTC
We need both a mysql schema and to change some postgres specific
things in the code, so a schema would be a good start I guess :)

 
Comment 7 Richard Hult 2004-02-07 21:57:12 UTC
Created attachment 24194 [details]
Schema from Lars Brandi Jensen
Comment 8 Lincoln Phipps 2004-03-08 00:27:50 UTC
Just done a lot of this too while getting to the bottom of the
dns_name issues . Don't think it will be too hard to look at doing the
MySQL provider (he says !) support given we've now got a schema.

I'm suggesting a dialog option of chooseing which database type to use
(out of a preset list which is the provider string). The PostgreSQL
provider is currently defined in 3 places in Planner. 
Comment 9 Alvaro del Castillo 2004-06-17 05:51:59 UTC
gnome-db has widgets to control the access to database, so we can reuse them as
isolated applicatiosn or borrowing the code from gnome-db ;-)
Comment 10 Lincoln Phipps 2004-06-17 08:27:08 UTC
re: MySQL - I discovered after I dug around the code
why MySQL isn't being used right yet. Its only in MySQL 5 with the
stored procedures that MySQL supports cursors (of which
the Planner code uses) though its since MySQL 3.23.44
that itz got the foreign keys but these are in the InnoDB
tables.

There may also be some sequences that may not be
the same but that could be coded around.

So its really when MySQL 5 is released and you would have
to use InnoDB tables, that Planner + MySQL could get
closer. As for ODBC ? - I'd have to let others comment on
how hard that would be to have Planner talk to a ODBC
connector. 
Comment 11 Bernhard Rohrer 2006-12-18 10:33:09 UTC
hmm, any news guys?
Comment 12 GNOME Infrastructure Team 2021-06-09 20:27:38 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/World/planner/-/issues/31.