Re: Reliably reproducing Native Exception 0xc0000005 on SQL CE 2.0
- From: "Ken" <kmsuzuki@xxxxxxxxx>
- Date: 8 Apr 2005 11:14:53 -0700
Darren - Thanks for taking a look at my SDF and reproducing this
problem. I've seen a number of people with this problem but no
solutions. I saw one thread in which a woman mentioned something about
constraints. Please let me know what the leading theories are on this
problem.
>why are you appending GUIDs together in a single column?
This is my implementation of the "Materialized Path" schema design for
storing hierarchical data. (http://dbazine.com/tropashko4.shtml is a
good reference).
>Why wouldn't this path be inherent in your logical data model?
I'm not exactly sure that I understand your question, but I'm
interpreting this as "Why don't you just use the typical Adjacency List
approach and use traversal to navigate the tree?" The main benefit of
Materialized Path is that given a node, you have the full path to the
root without having to refer to the database again.
.
- References:
- Reliably reproducing Native Exception 0xc0000005 on SQL CE 2.0
- From: Ken
- Re: Reliably reproducing Native Exception 0xc0000005 on SQL CE 2.0
- From: Darren Shaffer
- Reliably reproducing Native Exception 0xc0000005 on SQL CE 2.0
- Prev by Date: Problem when "Select" will not return any records
- Next by Date: Re: Filter rows at subscriber
- Previous by thread: Re: Reliably reproducing Native Exception 0xc0000005 on SQL CE 2.0
- Next by thread: dynamic snapshots - applying initial snapshot
- Index(es):