Windows 10 Anniversary Edition allows the user to remove the 260 character
limitation in MAX_PATH — any thoughts on updating the code to handle longer
paths?
Rail
-
___
sqlite-users mailing
ers-
>> bounces at mailinglists.sqlite.org] On Behalf Of Rail Jon Rogut
>> Sent: Tuesday, 5 April, 2016 21:55
>> To: SQLite mailing list
>> Subject: Re: [sqlite] SQLITE_IOERR_ACCESS with 3rd party DLL
>>
>> Hi Simon,
>>
>> Thanks for replying.
>
-
On Apr 6, 2016, at 2:57 AM, Olivier Mascia wrote:
>> Le 6 avr. 2016 ? 11:44, Rail Jon Rogut a
>> ?crit :
>>
>> I'm not at liberty to do that without their permission.. but I can tell you
>> that it's only 4 function
, at 9:58am, Rail Jon Rogut
> wrote:
>
>> That I can demonstrate all day long.. but I'd have to show that the issue is
>> their library causing the issue, so I'd need to demonstrate the shell
>> executing the commands okay without their library attached.
>
> Okay,
-
On Apr 6, 2016, at 2:11 AM, Olivier Mascia wrote:
>> Le 6 avr. 2016 ? 03:11, Rail Jon Rogut a
>> ?crit :
>>
>> So I statically compile Sqlite3 version 3.8.7.2 into my DLL using /MT
>>
>> I use
>>
>> #define SQLITE_THREADSAFE 1
&
, at 1:48 AM, Simon Slavin wrote:
>
> On 6 Apr 2016, at 9:41am, Rail Jon Rogut
> wrote:
>
>> I'll have to figure out a method to use the Shell Tools inside my program -
>> with the 3rd party DLL linked and running.
>
> I don't mean for production work. I mean you s
work - it's not included in the release build.
Cheers,
Rail
-
On Apr 5, 2016, at 10:29 PM, Simon Slavin wrote:
>
> On 6 Apr 2016, at 3:28am, Rail Jon Rogut
> wrote:
>
>> You'll notice I don't get an error at sqlite3_
s my code at fault -- but I can't see
anything I'm doing wrong.
> I consider this a bug but have been told that there's no appropriate way to
> fix it until SQLite4 comes along.
So you're saying I'm basically screwed :)
Thanks,
Rail
-----------
party DLL and
run the exact same code it's fine.
Thanks,
Rail
-
On Apr 5, 2016, at 6:43 PM, Simon Slavin wrote:
>
> On 6 Apr 2016, at 2:11am, Rail Jon Rogut
> wrote:
>
>> sql = pragma table_info('mytablename');
>&g
-- and neither cares
about the other so no trying to share code or data at all.
So to summarize? there's no disk corruption and the databases are fine.
Thanks,
Rail
-
On Apr 5, 2016, at 6:43 PM, Simon Slavin wrote:
>
> On 6 Apr 2016, at 2:11am, Ra
So I statically compile Sqlite3 version 3.8.7.2 into my DLL using /MT
I use
#define SQLITE_THREADSAFE 1
#define HAVE_USLEEP 1
When I use my DLL it works perfectly fine? However...
If I add a 3rd party LIB which also has Sqlite3 version 3.6.23.1 (I believe)
statically linked into it (also
11 matches
Mail list logo
