I've used blob(SQL Server image type) to insert files up to 2MB and did not forsee any size limitations. The way we do it is via Stored Procedures called with our own ODBC toolkit(using the ODBC32 DLL).
-----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de Michael Porter Envoy� : May 18, 2004 5:22 PM � : [EMAIL PROTECTED]; [EMAIL PROTECTED] Objet : RE: Labview, Linux and databases Interesting, I would love to see how you got ODBC to do BLOBs. Every ODBC implementation required the inserted data to be in the SQL statement and the maximum size for a single statement--which effectively limited inserts to a couple k. Mike... Michael Porter Porter Consulting, LLC. " ... after all He's not a tame lion... " -----Original Message----- From: Rolf Kalbermatter [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 18, 2004 03:11 To: 'Michael Porter' Cc: Info LabVIEW (E-mail) Subject: RE: Labview, Linux and databases "Michael Porter" <[EMAIL PROTECTED]> wrote: >Second, what kind of data are you going to be storing? If you are going to >be working with large datatypes like images or waveforms, you have a much >more fundamental problem--ODBC won't work for even Windows. My personal >opinion is that ODBC's inherent limitations make it unsuitable for any sort >of serious work unless it's your absolute last hope. I don't agree on this one. There are certainly problems possible with storing bigger than (usually 65k) of data in one single BLOB field but it all depends on the DB and the tools used. The biggest problem on the client side is that some DB don't support BLOB and if they do the format how to do it is not always the same. Also there are certainly ODBC drivers which simply fail above 32k or 65k. And last but not least having an ODBC interface on your client side which can cope with this is also not always standard. We have had applications where waveforms or complete graphic images were stored into an SQL Server database through ODBC and after some tweaking it worked fine including retrieving the data, although using our own LabVIEW ODBC interface may be one of the reasons it did work. The biggest problem is probably that eventhough BLOBs are supported in some databases, relational databases are not very well suited to store BLOBs. It can be done but is certainly not for what they were normally designed. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED] Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may contain privileged information. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information confidentielle: Le pr�sent message, ainsi que tout fichier qui pourrait y �tre joint, sont envoy�s � l'intention exclusive de son ou de ses destinataires; ils sont de nature confidentielle et peuvent constituer une information privil�gi�e. Nous avertissons toute personne autre que le destinataire pr�vu que tout examen, r�acheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'�tes pas le destinataire pr�vu, veuillez en aviser imm�diatement l'exp�diteur par retour de courriel et supprimer ce message et tout document joint de votre syst�me. Merci.
