"P Kishor" replied...
> On 2/7/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>>
>> "P Kishor" asked...
>>
>>
>> >I don't understand your question at all.
>>
>> I will answer it at the end.
>>
>> > On 2/7/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Greetings.
>> >>
>> >>
On 2/7/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>
> "P Kishor" asked...
>
>
> >I don't understand your question at all.
>
> I will answer it at the end.
>
> > On 2/7/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
> >>
> >> Greetings.
> >>
> >> I would like to have the results of a
Yes choice is good, Either way I'm greatful for an Excellent Tool, I can
workaround and Live without strict Affinity. But the option to enable it would
be a welcome feature.
Would there be any performance implications of Strict Affinity, either positive
or negative?
Samuel Neff <[EMAIL
But the important point is that no matter how much discussion we have, we
will never all agree that untyped is better than typed or that typed is
better than typed. That's why an option so individual developers can choose
is good. We don't have to agree, with an option we can agree to disagree.
On 2/8/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>
> "P Kishor" replied...
>
>
> > On 2/7/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
> >>
> >> "P Kishor" asked...
> >>
> >>
> >> >I don't understand your question at all.
> >>
> >> I will answer it at the end.
> >>
> >> > On 2/7/08,
Mike McGonagle wrote:
>
> Could you site a reference on this? I have been looking for documentation on
> how SQL deals with quoted things for a while now, but have not found
> anything.
>
Mike,
Standard SQL is defined by several different standards; SQL-92,
SQL:1999, and SQL:2003. Ultimately
Nathan Biggs wrote:
> Does anyone know where there is information on adding custom functions
> to sqlite? I have been using the CreateAggregate function to define my
> custom function, but just wanted to see if it was faster by re-compiling
> sqlite with the function in it already. I have the
<[EMAIL PROTECTED]> wrote:
> Hi..
>
>we are using sqlite3.3.4 with Integrity OS. we are facing a problem
> where in the VFS memory is getting exhausted due
>to large lock/unlock calls made by sqlite. Integrity support team
> said that, for each file lock call made by sqlite, a definite
Does anyone know where there is information on adding custom functions
to sqlite? I have been using the CreateAggregate function to define my
custom function, but just wanted to see if it was faster by re-compiling
sqlite with the function in it already. I have the sqlite source code
and
Hi,
We are working on different operating system other than unix and windows.
We are using the os_win.c for porting, we have ported the code by making
some changes with respect to the FAT32 file system apis in the code.
We have not tested much, my worry is whether we also need to take care of
[EMAIL PROTECTED] wrote:
>
> There are no lock leaks. But on the other hand, there is not
> a one-to-one mapping of lock to unlock calls. unlock is called
> more often than lock and there are often attempts to unlock files
> that have never been locked, irrc. This is harmless on windows
> and
Dennis Cote <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > There are no lock leaks. But on the other hand, there is not
> > a one-to-one mapping of lock to unlock calls. unlock is called
> > more often than lock and there are often attempts to unlock files
> > that have never
* Dennis Cote:
> The OP said they were measuring an excess of lock calls. That would
> imply that SQLite is locking files it has already locked. Is that
> possible with the POSIX APIs?
SQLite uses fcntl-based locks, which keep a separate lock for each byte
in a file (or, more precisely, any
I found that it was a fairly simple change to Sqlite to stop it changing
formats and causing grief. Out of the box it merges nicely with
scripting environments like Javascript, Python and TCL but can be a pain
in other places. Fortunately the changes needed where format changes
are
I would like to have strict affinity mode too. In our schemas we use check
constraints to enforce strict affinity. Unless you're working in a dynamic
typed environment, I can't imagine why you would want to have inconsistent
data within a single database field. Also for consistency with
"P Kishor" wrote...
> On 2/8/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>>
>> "P Kishor" replied...
>>
>>
>> > On 2/7/08, jose isaias cabrera <[EMAIL PROTECTED]> wrote:
>> >>
>> >> "P Kishor" asked...
>> >>
>> >>
>> >> >I don't understand your question at all.
>> >>
>> >> I will answer
I second the strict affinity mode as an optional feature, for the same reasons
as Lee.
A while back I ran into a problem while using the bit and feature of sqlite
and got unexpected results because sqlite changed the type from a 64bit integer
into a real. (I think)... In this case it would
Brad House <[EMAIL PROTECTED]> wrote:
> >> they have put traces and identified that for 1000 lock calls
> >> there are only 950 unlock calls, which is a shortage of 50 unlock
> >> calls.
> > The os_unix.c backend to SQLite makes no attempt to match lock/unlock
> > calls, because posix does not
I agree. After many years with SQL Server and Oracle (but new to
SQLite), the concept of storing different datatypes within the same
field is something I've had difficulty grasping. I'm not saying it's a
bad thing, but from a business perspective I can't think of a situation
where we would not
Is there any ways to find out locking details after getting the message?
sqlite3_get_table(db, ...
errmsg=database is locked
Dusan Gibarac
___
sqlite-users mailing list
sqlite-users@sqlite.org
>> they have put traces and identified that for 1000 lock calls
>> there are only 950 unlock calls, which is a shortage of 50 unlock
>> calls.
> The os_unix.c backend to SQLite makes no attempt to match lock/unlock
> calls, because posix does not requires such. If you are running
> on an
21 matches
Mail list logo