Re: [sqlite] Re: Re: Merging two tables
Thanks, i will go through it. regrads ragha ** This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! * - Original Message - From: Dennis Cote <[EMAIL PROTECTED]> Date: Tuesday, September 11, 2007 4:39 am Subject: Re: [sqlite] Re: Re: Merging two tables > RaghavendraK 70574 wrote: > > In sqlite3_create_function, xFunc func pointer signature does not > > allow to have a return value.Any other possible way achieving it > > apart from collation? > > > > > > > The result of your custom function is not returned directly by the > xFunc > function. your xFunc function must call one of the sqlite3_result_* > functions (see > http://www.sqlite.org/capi3ref.html#sqlite3_result_blob). > For a boolean result you would use sqlite3_result_integer and > return a > value of 1 for true or 0 for false. > > For more information see section 2.3 of > http://www.sqlite.org/capi3.html > and the func.c source file at > http://www.sqlite.org/cvstrac/fileview?f=sqlite/src/func.c=1.174 > which > uses these APIs to implement all the built in SQL functions. > > HTH > Dennis Cote > > > > - > To unsubscribe, send email to [EMAIL PROTECTED] > > - > > - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] Re: Re: Merging two tables
RaghavendraK 70574 wrote: In sqlite3_create_function, xFunc func pointer signature does not allow to have a return value.Any other possible way achieving it apart from collation? The result of your custom function is not returned directly by the xFunc function. your xFunc function must call one of the sqlite3_result_* functions (see http://www.sqlite.org/capi3ref.html#sqlite3_result_blob). For a boolean result you would use sqlite3_result_integer and return a value of 1 for true or 0 for false. For more information see section 2.3 of http://www.sqlite.org/capi3.html and the func.c source file at http://www.sqlite.org/cvstrac/fileview?f=sqlite/src/func.c=1.174 which uses these APIs to implement all the built in SQL functions. HTH Dennis Cote - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] multiple connections
--- Christian Smith <[EMAIL PROTECTED]> uttered: > As we saw when 3.3.0 was release with a non-backword compatible change in > storing booleans... Not quite the same. That was an intentional design decision they made at the time. As for bugs and unintended incompatibilities, you're always going to miss something. Few test code out of CVS. Most people only notice when the software is released. Some won't even bother to download and test the alpha, so their bug reports are delayed until the next stable release. Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list=396545433 - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] multiple connections
Joe Wilson uttered: --- "D. Richard Hipp" <[EMAIL PROTECTED]> wrote: In 3.5, cache can be shared between all threads, but shared cache is still disabled by default. You have to invoke sqlite3_enable_shared_cache() to turn it on. I put a comment in the documentation that we might turn shared cache on by default in future releases. But until I better understand the backwards compatibility issues, I think it is probably better to leave it off for now. There's no quicker way to see if there's a problem than enabling it in a release by default. ;-) As we saw when 3.3.0 was release with a non-backword compatible change in storing booleans... Christian -- /"\ \ /ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL X - AGAINST MS ATTACHMENTS / \ - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] HELP - CREATING A SQLITE3 BINARY INSTEAD OF A BASH
Thanks Joe and Dan Yes, I now have the binary file. Much appreciated - Uma Joe Wilson <[EMAIL PROTECTED]> wrote: autoconf generates the sqlite3 script when libsqlite3.so is used to set up the LD_LIBRARY_PATH. To avoid this, build a static sqlite3. ./configure --disable-shared make clean make sqlite3 optional: file sqlite3 ldd sqlite3 --- Uma Krishnan wrote: > I'm trying to debug sqlite3. But in order for me to do that, I need sqlite3 > binary. The makefile > generates a bash file. I'm confused as how that happens. After all, gcc is > used to generate > sqlite3 executable Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] HELP - CREATING A SQLITE3 BINARY INSTEAD OF A BASH
autoconf generates the sqlite3 script when libsqlite3.so is used to set up the LD_LIBRARY_PATH. To avoid this, build a static sqlite3. ./configure --disable-shared make clean make sqlite3 optional: file sqlite3 ldd sqlite3 --- Uma Krishnan <[EMAIL PROTECTED]> wrote: > I'm trying to debug sqlite3. But in order for me to do that, I need sqlite3 > binary. The makefile > generates a bash file. I'm confused as how that happens. After all, gcc is > used to generate > sqlite3 executable Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] HELP - CREATING A SQLITE3 BINARY INSTEAD OF A BASH
On Mon, 2007-09-10 at 10:01 -0700, Uma Krishnan wrote: > Hello, > > I'm trying to debug sqlite3. But in order for me to do that, I need sqlite3 > binary. The makefile generates a bash file. I'm confused as how that happens. > After all, gcc is used to generate sqlite3 executable > > Any pointers will be much appreciated. Autoconf weirdness. The binary is hiding in the ".libs" directory. Or maybe it's ".lib". I forget. - To unsubscribe, send email to [EMAIL PROTECTED] -
[sqlite] HELP - CREATING A SQLITE3 BINARY INSTEAD OF A BASH
Hello, I'm trying to debug sqlite3. But in order for me to do that, I need sqlite3 binary. The makefile generates a bash file. I'm confused as how that happens. After all, gcc is used to generate sqlite3 executable Any pointers will be much appreciated. Thanks Uma
Re: [sqlite] extension-functions.tgz for sqlite3 3.4.1 ?
--- Liam Healy <[EMAIL PROTECTED]> wrote: > Thanks for the tip Joe. With sqlite3.h included, I can eliminate os.h and > vdbeInt.h, but not sqliteInt.h. Apparently sqliteInt.h is not included by > sqlite3.h, and there are typedefs there that are needed. It would be nice if people could use the extension functions with the amalgamation, consisting of just sqlite3.h and sqlite3.c. If you use sqliteInt.h, they can't do that. Why not just repeat the typdefs for u8, etc, in your module? Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting - To unsubscribe, send email to [EMAIL PROTECTED] -
Re: [sqlite] extension-functions.tgz for sqlite3 3.4.1 ?
Thanks for the tip Joe. With sqlite3.h included, I can eliminate os.h and vdbeInt.h, but not sqliteInt.h. Apparently sqliteInt.h is not included by sqlite3.h, and there are typedefs there that are needed. Liam On 9/5/07, Joe Wilson <[EMAIL PROTECTED]> wrote: > > Hi Liam, > > In func_ext.c and map.h you're including private sqlite3 header > files: sqliteInt.h, os.h and vdbeInt.h, which change from release > to release. > > If you only use the public sqlite3.h header file instead, it has > a greater chance of being compatible with new releases. > > --- Liam Healy <[EMAIL PROTECTED]> wrote: > > OK I have posted a new version of extension-functions.tgz on > > sqlite.org/contrib. This version includes definitions for READ_UTF8, > > sqlite3ReadUtf8, SKIP_UTF8, sqlite3utf8CharLen, xtra_utf8_bytes, > > xtra_utf8_bits, utf_mask taken from the 3.3.13 source code, so it should > > continue to work in sqlite 3.4. > > >
