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 786752 - GdaTimestamp is private. Should be public
GdaTimestamp is private. Should be public
Status: RESOLVED NOTABUG
Product: libgda
Classification: Other
Component: general
5.2.x
Other Linux
: Normal normal
: ---
Assigned To: malerba
gnome-db Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-08-24 12:44 UTC by Pavlo Solntsev
Modified: 2017-11-04 20:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Proposed patch (2.44 KB, patch)
2017-08-24 12:44 UTC, Pavlo Solntsev
none Details | Review

Description Pavlo Solntsev 2017-08-24 12:44:41 UTC
Created attachment 358334 [details] [review]
Proposed patch

Compilation error was because of undefined type for GdaTimestamp.
Comment 1 Pavlo Solntsev 2017-08-30 04:05:40 UTC
Can someone throw a comment here. What should I wait for? My commit via GitHub pull request was rejected. Therefore, I created this bug report record. I did something wrong? Please advice. I have some other ideas for libgda modifications, but I afraid to push them until I totally understand the "contribution" process. Thanks.
Comment 2 Murray Cumming 2017-11-03 18:35:49 UTC
What problem does this patch solve? You might mention that in the git commit message if you submit this as a git commit patch. For instance, you might use

  git format-patch HEAD^
Comment 3 Pavlo Solntsev 2017-11-03 21:18:35 UTC
Murray,
I was trying to compile the library and got problem with GdaTimeStamp object. The solution was to move the declaration of the object from *.c (prvate) to *.h (public) scope. I just checked up to date master and this problem is not applicable anymore. I can't reproduce it. However, unless there is a reason to keep GdaTimeStamp private it may be moved to header. It looks like, this bug should be closed. Thank you for advice with patch generation. Will do better next time. Thanks.
Comment 4 Murray Cumming 2017-11-04 20:38:54 UTC
The change seems to be intentional, though I'm not sure why for such a simple struct. You can now use the various get functions instead.

Note that the API in git master is unstable, meaning that it can change.