Re: [gnome-db] GDA_CONNECTION_OPTIONS_THREAD_SAFE issue.

On Wed, 2009-08-26 at 10:26 +0200, Vivien Malerba wrote:

> 2009/8/26 Bas Driessen <[email protected]>:
> > On Tue, 2009-08-25 at 19:33 +0200, Vivien Malerba wrote:
> >
> >
> > 2009/8/14 Bas Driessen <[email protected]>
> >
> > Hi Vivien,
> >
> > You recently introduced the GDA_CONNECTION_OPTIONS_THREAD_SAFE option. There
> > is a problem with this that if set and a partial meta store update is
> > performed, the meta store is not updated. If using any of the other
> > GDA_CONNECTION_OPTIONS all works fine.
> >
> > I have attached 2 small c programs to re-produce this issue. The database
> > provider is MySQL, my (test) database is called  'stock' and the DSN is
> > 'mystock'
> >
> > -1 rm /tmp/mysql_meta.db
> > -2 in MySQL: drop table xPartsUC;
> > -3 Run mysql_full (source attached)
> > -4 in MySQL: CREATE TABLE xPartsUC (Part_ID varchar(5) PRIMARY KEY,
> > Description varchar(30));
> > -5 Run mysql_partial (source attached)
> > -6 sqlite3 /tmp/mysql_meta.db  then run: select * from _tables where
> > table_name = '"xPartsUC"';
> > -7 nothing there. Run mysql_full and the entry is there.
> >
> > The cause of this problem was that I had forgotten to implement a virtual
> > method. This should now be fixed in the master branch, can you check?
> >
> >
> > Initial testing shows that this is working OK now. Will hit it a bit harder
> > over the next couple of days, but it looks like this bug is fixed.
> >
> 
> Ok, great.
> 
> BTW, next time you find a bug it'd be better if you could file a bug
> report in bugzilla at http://bugzilla.gnome.org/, as it's then easier
> to follow its correction and keep an history than in a mail.


No problem Vivien. Was not sure if bugs in bugzilla were actually
followed up, therefore the mailing list requests. Will channel them
through bugzilla in the future as requested.

Bas.

_______________________________________________
gnome-db-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gnome-db-list