RE: [sqlite] Using SQLlite as a db in an IIS website directory

2004-10-26 Thread Roger Hawkins
Thks for the info..

How do I find out which account IIS is running under?

Cheers ;~)

> -Original Message-
> From: CARIOTOGLOU MIKE [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, 26 October 2004 10:07 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: [sqlite] Using SQLlite as a db in an IIS website 
> directory
> 
> 
> first, find out which account IIS is running under. chances 
> are it is IUSR_. then, go to the directory the 
> DB is in (the file system, NOT the IIS virtual root), and 
> give full rights to this account. if this does not work, do 
> the same for the IWAM_ account.
> 
> also, check that the virtual directory you are accessing the 
> db from (in IIS setup), was WRITE permissions enabled.
> 
> > -Original Message-
> > From: Roger Hawkins [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 26, 2004 3:05 PM
> > To: [EMAIL PROTECTED]
> > Subject: [sqlite] Using SQLlite as a db in an IIS website directory
> > 
> > 
> > Hi,
> > 
> > On my win2000 Pro machine everything works fine running 
> SQLlite using 
> > SQLite.net as a database for a web application.
> > 
> > On my 2003 server however I get:
> > 'attempt to write a readonly database' when trying to perform 
> > a write to
> > the db. I can read from db fine.
> > 
> > There appears to be nothing obvious permissions wise I can see that 
> > should be causing a problem.
> > 
> > In each case the database is in a directory beneath the
> > website virtual
> > directory. It appears to be some permission problem but I cannot see
> > anything obvious.
> > 
> > Any ideas would be greatly appreciated.
> > 
> > cheers,
> > Hawkeye
> > 
> 
> 
> 




[sqlite] Using SQLlite as a db in an IIS website directory

2004-10-26 Thread Roger Hawkins
Hi,

On my win2000 Pro machine everything works fine running SQLlite using
SQLite.net as a database for a web application. 

On my 2003 server however I get: 
'attempt to write a readonly database' when trying to perform a write to
the db. I can read from db fine.

There appears to be nothing obvious permissions wise I can see that
should be causing a problem. 

In each case the database is in a directory beneath the website virtual
directory. It appears to be some permission problem but I cannot see
anything obvious.

Any ideas would be greatly appreciated.

cheers, 
Hawkeye




RE: [sqlite] Resetting primary key auto-increment after table re-create

2004-03-08 Thread Roger Hawkins
Sorry...That's what I meant - scary you can insert into a table that has
this property without first setting The propert off without re-seeding -
ie. How Sybase and SqlServer handle this..

It would be good if this was documented a little clearer  

Thx all for your assistance - onward and upward (so to speak)

Cheers...

> -Original Message-
> From: Kurt Welgehausen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 9 March 2004 2:34 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [sqlite] Resetting primary key auto-increment 
> after table re-create
> 
> 
> > So what you are saying is that if I recreate the table I can insert
> > all the old values back into the newly created table (including the 
> > primary key values) and the primary key column wont 
> complain? That's a
> > bit scary!
> 
> It's not scary, it's essential.  In a real database, an
> integer primary key will almost always be referenced by one 
> or more foreign keys.  Changing the primary key would destroy 
> referential integrity.
> 
> Regards
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [sqlite] Resetting primary key auto-increment after table re-create

2004-03-07 Thread Roger Hawkins

Thanks for your reply...
I havent found any reference to this in the doco so Im not sure how any
of this might work..

So what you are saying is that if I recreate the table I can insert all
the old values back into the newly created table (including the primary
key values) and the primary key column wont complain? That's a bit
scary!

Even if this is true what happens when I next insert a value (normally
without specifying the primary key field) - does it just pick up the
latest?

I guess I will have to try this but it all sounds a little confusing...

Any one tried this?

> -Original Message-
> From: Will Leshner [mailto:[EMAIL PROTECTED] 
> Sent: Monday, 8 March 2004 3:47 PM
> To: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
> Subject: Re: [sqlite] Resetting primary key auto-increment 
> after table re-create
> 
> 
> 
> On Mar 7, 2004, at 8:51 PM, Roger Hawkins wrote:
> 
> > turning off of auto-incremement
> > then I do my insert of old table rows into new table
> > and then turning back on auto-increment with a seed value (starting
> > point)
> > would be the way to go.
> >
> 
> If you specify a value for the primary key when you do the 
> insert, then 
> that is the value that will be used (assuming it is unique). 
> Won't that 
> work?
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]