thanks for mentioning it. there are some non-blocking mysql client implementations I could have a look at but first I'll try the blocking version and see how it performs.
> Gesendet: Dienstag, 23. Januar 2018 um 11:21 Uhr > Von: "IOhannes m zmoelnig" <zmoel...@iem.at> > An: pd-list@lists.iem.at > Betreff: Re: [PD] MySQL Pd external? > > On 2018-01-23 11:05, Christof Ressi wrote: > >> i guess the main issues with an mysql external is that it breaks all > >> realtime constraints. > > > > so does [soundfiler]. for things like initializing/saving it won't matter, > > but you're right, constantly polling the DB in the audio thread is probably > > not a good idea. > > > >> which is about one message away in pyext. > > > > yes, but isn't this true for many things we do in Pd? :-D > > oh definitely. > > i'm not trying to prevent a [mysql] external. > > however, from my very long lasting memory on and of the pd-list, i do > remember that the blocking issue was indeed mentioned and discussed in > conjunction with "some SQL" external. > some things change, but some things don't. > > fgasdmr > IOhannes > > _______________________________________________ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > _______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list