I work with connection pool, a threaded control to provide avail connections.
Best regards, JB José Benedito JBS Soluções Consulting Systems Development c <josebened...@gmail.com>ont...@jbsolucoes.net www.jbsolucoes.net skype: s...@jbsolucoes.net +55 22 30251654 +55 22 996064279 On Mon, Feb 2, 2015 at 6:05 AM, Michael Schnell <mschn...@lumino.de> wrote: > On 01/30/2015 10:56 PM, Fabrício Srdic wrote: > >> Hello, >> >> The DB access framework of the fpc is not thread safe. >> > > IMHO you should never use the therm thread save in such a generalization. > You need do be a lot more specific. > > I never took a look at "The DB access framework of the fpc", so I can't > comment on this but e.g. TList obviously is not thread save (that is why we > have TThreadList), but anyway it's no problem to instantiate a TList object > and use that exclusively from a single Thread, and then instantiate another > TList object and use that exclusively from a different single Thread. Hence > you could say "TList is thread save but it's instantiations are not". Maybe > it's similar with "the DB framework". > > AFAIK, Indy is thread save (of course provided the user adheres to a lot > of necessary precautions that might not be explicitly documented). > > I do know that a friend of mine used Delphi and Indy with a heavily > multithreaded project. > > -Michael > _______________________________________________ > fpc-pascal maillist - fpc-pascal@lists.freepascal.org > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal >
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
