text:
Team Perfect Locks headed out to the Big Apple during Fashion Week. We had the great pleasure of sponsoring products to be used in several fashion designer's 2014 Spring and Summer collections, including the winner of Project Runway Season 5, Leanne Marshall. The 3 day event was featured at the Helen Mills Event Space located in Manhattan's Art District… Host to well known designers such as Yves Saint Lauren, Hugo Boss, and Valentino. Perfect Locks also sponsored Haute Couture designer Carlos Alberto, and Project Runway Season 5 first runner-up and fan favorite Korto Momolu.
We were very proud to sponsor this event with beauty giant Aveda, among other notable brands. We provided over 45 runway models various pieces, including clip on extensions and volumizers. The side swept ponytails were a big hit. Colors including bright blondes, rich brunettes, and vibrant auburn tones.The Aveda team styled made each and every runway model look both glamorous and elegant on the runway. Perfect Locks also included samples of our Vital Hair Care collection and pieces from new eyelash collection labeled "Perfect Lashes" which has not yet been released to the public.
The venue generated an attendance of 5000 guests over 3 days. The 3 fabulous designers showcased showcased their latest designs using creative colors and shapes. From luxurious cream gowns with overflowing layers, to bright colors with sharp lines and modern overtones, the looks received much applause from the energetic audience. Leanne Marshall's Spring 2014 collection featured a feminine color scheme and chiffon. The models glided down the runway in stunning taupe, lavender, and pink variations… Each dress displaying more and more detail. We were especially fond of the draped flounces and deep necklines.
This was the first Fashion Week event that Perfect Locks has sponsored, as well as our first trip to New York as a team. The experience was unparalleled, and will most certainly be the first of many trips to the amazing city of New York. We would like to thank you for taking a moment to experience this journey with us.


text:
UCLA Journal of International Law and Foreign Affairs (JILFA) Annual Symposium
UCLA's JILFA hosts an annual symposium addressing pressing issues in international law. This year, the focus is the so-called BRICS countries: Brazil, Russia, India, China, and South Africa. The BRICS are contributing to significant changes in the world's economic alignment, but each country deals with several serious human rights issues. JILFA has invited leading academics and practitioners to speak about racial discrimination in Brazil, freedom of speech and expression in Russia, violence against women in India, minority rights in China, and LGBT rights in South Africa.
For more information on the schedule of this event consult the JILFA website.
Cost: Free and open to the public; pay-by-space and all-day parking ($11) available in lot 3.
Contact Sandeep Prasanna (firstname.lastname@example.com) or Tanya Sukhija (firstname.lastname@example.com) for more information on behalf of JILFA.
African Studies Center Tel: 310-825-3686
Sponsor(s): UCLA Journal of International Law and Foreign Affairs
© 2013. The Regents of the University of California. All rights reserved.
Terms of Use / Privacy Policy

subset: commoncrawl


text:
The industrial area's of Mujjesar, Sector 6 and Ballabgarh are easily accessible from here. The market area is close by. The hotel is comfortable but the food is great. Good bargain! This is a 2 star property, do not expect extravagance in anyways.
- Also Known As:
- Mahalakshmi Palace Hotel Faridabad, Haryana
- Reservation Options:
- TripAdvisor is proud to partner with Booking.com and MakeMyTrip so you can book your Mahalakshmi Palace Hotel reservations with confidence. We help millions of travellers each month to find the perfect hotel for both holiday and business trips, always with the best discounts and special offers.


text:
Triple-negative breast cancers lack the presence of the estrogen receptor, progesterone receptor, and HER2/NEU protein. This subtype of breast cancer can be aggressive, difficult to treat, and more likely to recur than other subtypes of breast cancer. Obesity can increase the risk of breast cancer by causing breast inflammation, which has been linked to cancer. The purpose of this study is to see if treatment with docosahexaenoic acid (DHA) in overweight and obese survivors of triple-negative breast cancer for six months reduces the amount of inflammation in the breast. If the effects are significant, it might be possible to use DHA to reduce the risk of breast cancer development and recurrence.
DHA is a fatty acid that is present in some foods (such as fatty fish) and in fish oil supplements. DHA is known to inhibit cancer-fueling chemicals produced by certain immune cells that accumulate in inflamed breast tissue. It is not yet known if DHA can reduce the risk of breast cancer.
Participants in this study will be randomly assigned to receive either DHA capsules or placebo (sugar) capsules. Researchers will compare the levels of certain "biomarkers" of inflammation in the blood and breast tissue in both groups.
To be eligible for this study, patients must meet several criteria, including but not limited to the following:
For more information and to inquire about eligibility for this study, please contact Dr. Ayca Gucalp at 646-888-4538.


text:
Myth of in-experience: Case Study: Joe Kocur
Would like to try and dispel this myth that age and in-experience plays a role in explaining a bad performance. More often than not it is a charade used to mask a loss, oft times an embarrassing loss by some of the more rabid and less objective. Lets use Joe Kocurs lead up to his shot in the NHL as a case study. What was Joey doing before he got to the big dance? Dishwasher? Painter? Architecht? Nuclear scientist? Why no, of course not. Here is a hint:
WHL, AHL, IHL opponents to name a few: Lyndon Beyers, Ken Baumgartner, Stu Grimson, Mark Tinordi, Val James, Craig Coxe, Kevin McGuire, Marty McSorely, Archie Henderson, Serge Roberge
Fear always springs from ignorance." -Ralph Waldo Emerson |
The above post may contain sarcasm. Brashear beat your favorite fighter. Undisputed top 5 all time. |
Peter Ing
The Following User Says Thank You to nilan30 For This Useful Post: | ||
blockerpunch (11-29-2012) |
The Following User Says Thank You to acdcrocksno1 For This Useful Post: | ||
RetardedChimp (11-28-2012) |
LOL - your ad-hominem attack of me instead of the proposition is as all intelligent and informed people know is cowardly and evasive - pathetic
Fear always springs from ignorance." -Ralph Waldo Emerson |
Your proposition is a waste of time and deserves no valid response. I've given a million and one intelligent and infrormed post on your subjects but yet you still beat the same dead horse over and over and over and over and over and over
You have enemies? Good. That means you've stood up for something, sometime in your life. -Winston Churchill |
The Following User Says Thank You to acdcrocksno1 For This Useful Post: | ||
RetardedChimp (11-28-2012) |
Now this is staggering
(Referring to a glass of water) I mixed this myself. Two parts H, one part O. I don't trust anybody! --Steven Wright |
The Following User Says Thank You to brawl lover For This Useful Post: | ||
RetardedChimp (11-28-2012) |
You have to look at someones career because every fighter is different. Some people came into the league ready for anything, Wilson and Probert come to mind, while others needed to learn in the NHL, Grimson and McSorley come to mind. Marty was 4-8-4 in his rookie year. Anybody with an ounce of knowledge knows He is a much better fighter than that record. So how is it possible that age and inexperience did not play a role in his rookie season? Holding someone accountable every time they fight is your prerogative. Saying age and inexperience does not play a role for most of these guys is way off base. And to judge every single fight with blinders on like there are no variables just gives a break to those who only fought when they wanted to while diminishing the accomplishments of those that fought at times they obviously did not want to, or for much longer than others. Like Probert, the best ever!
Here in this hopeless fXcking hole we call LA The only way to fix it is to flush it all away. Any fXcking time. Any fXcking day. Learn to swim, I'll see you down in Arizona Bay. |
The Following 5 Users Say Thank You to pesadillamal For This Useful Post: | ||
battleship25 (11-28-2012), blockerpunch (11-29-2012), BullyFan (11-28-2012), I like Boobs (11-28-2012), srehm1 (11-28-2012) |
As I said if McKenzie, Simon, Brown, Kocur, Probert, come from the world of ballet right into the NHL, yeah they have an excuse....learning the proclivities and styles, habits of your opponents is homework.
Fear always springs from ignorance." -Ralph Waldo Emerson |
Then how do we explain the early woes of Grimson, Brashear, Ray, Cairns, McSorley-all of them became great fighters. A few of them can even claim to have been champ at some point in their respective careers. All of the above fought all the way through juniors/minors and sometimes against the same fighters they would later face in the NHL. Many struggled with physical issues-McSorley was very lean in those first few years in pittsburgh and perhaps not up to snuff against stronger seasoned veteran NHL heavies. Grimson was noted for his iffy balance when he first broke in-yet after working on it and getting better and better-he became a top-10 fighter for a number of years. Cairns left his chin hanging right out there in those early years providing an easy target for opponents. Brash was a hugger with scared eyes-he later went on to become a dominant force in the league and a lock as a top-5 all-timer. If you told me this when he first broke in with montreal-I would have laughed in your face. i never would have imagined he could accomplish that considering the way he looked early in his career. Ray stated in his book that his infamous fight with Dave brown-with that big stunning right hand-gave him the confidence he needed to become a better fighter.
these are all examples of fighters who had slow starts to their careers-yet they went on to become great fighters. Not everyone is in their prime when they first break into the league. Some are great right off the bat like McCarthy, Wilson, Simon, Laraque, Mckenzie etc. Some need more experience-more fights, more trainining, more confidence in themselves. Sure they almost all were fighting in juniors or the AHL/minors-but they weren't fighting NHL HW's. I look at every fighter as being different. Everyone of them hits their peak at different times and begin to fade out at different times. It's all out there for us to see. No way was McCarthy the same fighter in Boston that he was in Calgary. Brashear was a totally different animal entirely with VAN/PHI/WAS than he was in Montreal. You simply cannot say that they are all the same from start to finish. that's painting with too broad a brush. Sure they were all fighting from day 1 in juniors but in juniors you are taking on 16, 17, 18 year olds-kids still growing into their bodies-not prime time NHL veterans. I'd also say that probert wasn't the champ from day one either. he had some growing pains as well (berube, ewen, fraser)-yet learned and gained in experience/confidence with every fight until he hit his prime in 87-88.
Don't whine when an enforcer actually enforces. |
The Following 9 Users Say Thank You to srehm1 For This Useful Post: | ||
battleship25 (11-28-2012), blockerpunch (11-29-2012), bruiser11 (11-29-2012), BullyFan (11-28-2012), I like Boobs (11-29-2012), mikebflorida (11-28-2012), pesadillamal (11-28-2012), Rampage76 (12-03-2012), RetardedChimp (11-29-2012) |
Fear always springs from ignorance." -Ralph Waldo Emerson Last edited by BaddaBing Badda Boom; 11-29-2012 at 10:41 AM. |
Thread Tools | |
Display Modes | |


text:
In the law of secured transactions, a person that, with respect to an obligation secured by a security interest in or an agricultural lien on some collateral owes payment or other performance of the obligation, has provided property other than the collateral to secure payment or other performance of the obligation, or is otherwise accountable for payment or other performance of the obligation.
Definition from Nolo's Plain-English Law Dictionary
The person or entity that owes an obligation to another (for example, the party that must pay on a promissory note).
Definition provided by Nolo's Plain-English Law Dictionary.
August 19, 2010, 5:20 pm


text:
My husband and I stumbled upon this gem while travelling through Locarno on our honeymoon! The price was right, as was the location. We loved that we were able to stroll into the city and leave our car parked at the hotel. Breakfast was great, and definitely had something available for everyone. Service was friendly and we had everything we... More
- Reservation Options:
- TripAdvisor is proud to partner with Booking.com and Priceline so you can book your Schlosshotel Locarno reservations with confidence. We help millions of travellers each month to find the perfect hotel for both holiday and business trips, always with the best discounts and special offers.


text:
Release 4.11
This document lists all changes for the most recent major release (releases with number X.Y) and subsequent minor releases (with numbers X.Y.Z and perhaps further identifiers), including major and important changes and a list of all user-visible modifications. Change History repeats the list of user-visible modifications for this release and includes similar lists for earlier releases.
The release described in the documentation set is 4.11.
Major Changes in release 4.11
[Added October 11, 2013] AllegroGraph supports Top Braid Composer 4.3 and 4.2. See Top Braid Composer Plugin. Note that there is no code or version change to AllegroGraph 4.11 for this update: just a new version of TBC is available.
Auditing support, see Auditing
Callimachus support, see Callimachus support
xsd:decimals can now be stored more efficiently and support exact computation.
The xsd:date representation has been enhanced to support optional timezones.
Works with Allegro CL 9.0 SMP Lisp, new direct and remote clients for Allegro CL 9.0 with and without SMP
Java connection pooling
The changes in the previous major release, version 4.10, are listed just below.
Major Changes in release 4.10
Along with bug fixes and other improvements, the major changes in release 4.10 are:
The Top Braid Composer Plugin (see Top Braid Composer Plugin) also now works with TBC version 4.0.x (it has been tested on 4.0.0). No change to AllegroGraph is required. Just change what you download, as described in Top Braid Composer Plugin. Note too TBC version 3.6.2 is no longer supported by Top Quadrant.
SPARQL parser speed has been improved
The Java client can now be configured to have sessions use the main server port rather than a dedicated port.
The changes in the previous major release, version 4.9, are listed just below.
Major Changes in release 4.9
New materializer, which generates triples by applying a set of rules to the current triples in the triple store and then places the resulting triples back in the triple store. For example, RDF-inferred triples can be generated before query-time rather than at query-time. See Materializer for more information.
SPARQL Query Improvements
Improved Memory Management Functionality
New License Key Features
New Experimental Webview Query Screen and Graph View
Changes in earlier releases
This document lists changes in the current release and several previous releases. See the Change History for a list of all changes in earlier releases.
AllegroGraph 4.11 user-visible changes
AllegroGraph Server: General Changes
Rfe12309 - Improve algebraic query manipulation
AllegroGraph now notices patterns of the form
(:join (:join A (:bgp B)) (:bgp C))
and transforms them into the equivalent
(:join A (:bgp B C))
(I.e., it merges the two BGPs). This transform brings more triple-patterns together which lets AllegroGraph order the query operations better.
Rfe12305 - Relative paths in the configuration file
Relative file or directory paths in the configuration file were always interpreted relative to the directory containing the configuration file. In this rfe, a BaseDir configuration directive was added that allows another path to be specified for this purpose. See the documentation in Server Configuration for more.
Rfe12280: Simplify geospatial type-mapping API
Geospatial subtype mappings can now be set up with the regular datatype and predicate mappings rather than needing to use the specialized functions. The old functions still work but are now unnecessary. They will be removed in some future release.
Rfe12260 - Automatically map temporal predicate data to xsd:dateTimes
Triple-stores created in this version of AllegroGraph will include the three AllegroGraph temporal predicates in the list of automatically mapped predicates. I.e., the objects in triples with these predicates:
- <http://franz.com/ns/allegrograph/3.0/temporal/endpoint>
- <http://franz.com/ns/allegrograph/3.0/temporal/startpoint>
- <http://franz.com/ns/allegrograph/3.0/temporal/time>
will be converted into encoded xsd:dateTime literals. This encoding makes range queries against them faster and makes it easier to use AllegroGraph's temporal functionality.
Rfe12259 - Optimize certain combinations of JOINs and FILTERs
The query engine now recognizes certain patterns of JOINs and FILTERs and rewrites them to be more efficient. For example, a pattern like
(:join A (:filter B f))
can often be better evaluated as
(:filter (:join A B) f)
Rfe12182 - More restrictive umask
With this change, users who aren't the owner of the file, or a member of the group of the file (that is, "other" users in chmod manpage terms) have no read, write or execute permission on files created by AllegroGraph.
On existing installations, it's recommended, but in no way enforced, to change permissions the same way with 'chmod -R o-rwx <directories>' where <directories> is the list of directories holding AllegroGraph data (LogDir, SettingsDirectory, catalog directories, etc).
Rfe12175 - Audit log
When the 'Auditing' global configuration directive is set to 'yes' (it defaults to 'no'), events that have implications on security or performance will be logged to the new system database in the new system catalog. Note that regardless of permissions only superuser can read or write the system catalog.
See Auditing for more information.
Rfe12151: Remove support for loading N-Triples into a federated triple-store
AllegroGraph 3 introduced some techniques that optimized loading of N-Triples into a federated-triple-store. These have been superseded in AllegroGraph 4 because agload
is significantly faster and easy to use.
Rfe12147: Better manage memory especially for large solutions
AllegroGraph now manages large query result sets (with or without DISTINCT or ORDER BY) more efficiently.
Rfe12138 - Agload: reduced memory footprint and other enhancements
Reduced memory consumption of agload processes. Particularly in the case where there are many input sources.
Agload now analyzes input sources on the fly. This means you will not necessarily encounter errors about invalid input sources prior to modification of a triple-store. Use --dry-run command line argument if you wish to pre-analyze an agload job.
Rfe12125 - Improve performance of unordered queries with small limits
AllegroGraph now uses chunk-at-a-time query processing for queries with small LIMITs that do not use ORDER BY more frequently. In particular, the chunkProcessingAllowed query option can now take three values:
- yes - use chunk-at-a-time mode whenever possible,
- no - always use single-set mode, or
- possibly - choose the execution mode that makes the most sense for the current query.
The default value for chunkProcessingAllowed has been changed from no
to possibly
Rfe12111 - Improve memory checking efficiency
Improve the efficiency of AllegroGraph's memory tracking code slightly.
Rfe12089 - Improve cursor resource management
Improve AllegroGraph's low-level cursor memory management.
Rfe12063 - Allow in-memory-triple-stores to use blank nodes
The in-memory-triple-store implementation for the remote-lisp-client was missing several methods required for full blank node support. This has been corrected.
Rfe11973: Improve usage of UPI-map
Improved the way AllegroGraph manages the use of secondary indexes (UPI-maps).
Rfe11955 - :commit argument added to delete-duplicate-triples
The :commit argument was added to delete-duplicate-triples to allow for the deleting a very large number of duplicates.
Rfe11886 - Use statistics more often when re-ordering query clauses
The query engine now uses store statistics in more places when working to reorder the clauses in a query's basic graph patterns (BGPs). This should produce better plans more often with less need for customer query tweaking.
Rfe11585 - Some queries unnecessarily accumulated partial results
AllegroGraph was sometimes accumulating results unnecessarily. For example, the query
select (count(*) as ?total) where {?s ?p ?o}
was accumulating the actual results even though only the summary was necessary.
Rfe11511 - Encode xsd:decimals
xsd:decimals used to be stored as strings. With this change, they are automatically encoded directly in the UPI which potentially brings significant savings in storage space and computation in queries. The most significant 20 digits are preserved by the encoding.
Note that this change only affects the encoding of new triples. To convert old triples and take advantage of the more efficient storage, the database contents must be reloaded from a serialized format. We recommend exporting in nquad format and then reimporting it with agload. Restoring from a backup is not sufficient.
Rfe11197 - Serialize triple IDs as resources rather than literals
Previously, a triple ID would have been serialized as a typed literal like
This format prevented the use of triple IDs in the subject of a triple so we have changed the serialization to a URI like
Any triple IDs already in a triple-store will remain the same (though they will print differently). This change does mean, however, than any files that contain triple IDs in the old format will need to be converted in order to be re-loaded (note, however, that the IDs assigned to triples are not part of any serialization format which means that they cannot reliably round-trip in any case).
Rfe10292 - Handle filename limit for unix domain sockets
Linux has a limit of 107 characters for filenames of UNIX domain sockets. With this change, when bumping into that limit, a meaningful error message is printed and the workaround of setting the UnixDomainSocketDirectory or the SettingsDirectory configuration directive to a shorter path is suggested.
Bug21793 - Fix race in inter process communication
Under extremely rare circumstances, multiple threads could end up listening on the same communication channel which can lead to errors and deadlocks. This was duly detected by an assertion that appeared in the log as:
the assertion (endp (intersection
This bug has been fixed.
Bug21782 - Potential double close of cursors
An inadvertent double close of cursors was discovered that could potentially result in improper sharing of a data structure. This has been corrected.
Bug21779 - Fix low-level cursor resourcing bug
Under heavy load, the secondary index (UPI-map) creation function could leak a cursor leading to potential resource problems. This has been corrected.
Bug21761 - Prolog q-
functor could be treated as q
If a reasoning triple-store can use secondary indexes (UPI-maps) then it was possible for AllegroGraph to treat some q-
functors as q
functors in a given Prolog select query. This has been corrected.
Bug21745 - Fix crash related to aggregate functions
Under rare circumstances, queries involving aggregate functions may cause the backend to crash. This bug has been fixed.
Bug21744 - Some Prolog select queries could return duplicate results
If using secondary indices (i.e., UPI-maps), it was possible for Prolog select queries that returned raw
UPIs to overwrite one solution with another. This problem could only occur with UPI only queries and never with queries that returned strings. The problem is now fixed.
Bug21740 - Rare hangs under high load
The message broker (called the "Hub" process) may get into a state where forwarding a message blocks, preventing all other messages from being handled. This bug has been fixed.
Bug21735 - Corrupted distinct results
Under rare circumstances, queries involving DISTINCT could produce results with the bindings assigned to the wrong variables. This bug has been fixed.
Bug21702 - XSD casting in a BIND could convert to xsd:integer incorrectly
Using an XSD cast in a BIND could loss the datatype and switch it to xsd:integer. E.g.,
BIND(xs:long(?test) AS ?testLong)
would bind ?testLong to a value whose datatype was xsd:integer rather than xsd:long. This has been corrected.
Bug21693 - Avoid forking too many blank node servers in agload.
Improves agload performance under default conditions when loading ntriples or nquads files which are small and numerous.
Bug21691 - Reasoning over subproperties of symmetric properties
AllegroGraph's RDFS++ reasoner partially failed to infer triples from sub-properties of a symmetric property. This has been corrected.
Bug21680 - Some BIND forms could be evaluated incorrectly.
A BIND form at the start of a BGP could fail to get values from earlier in the query evaluation.
For example, this form
?a a ?b .
{ BIND( ?b as ?otherB
?otherB a ?c .
could lose the binding for ?otherB. This has been corrected.
Bug21670 - FILTER and EXISTS could interact incorrectly.
Depending on the shape of the rest of the query, it was possible for a FILTER clause to be applied to the inside of an EXISTS or NOT EXISTS filter rather than being applied to the main body of the query. This has been corrected.
Bug21663 - Redo of new index creation confuses instance process
If a database with a newly-created index has been shut down uncleanly, restart of the database may crash. This has been corrected.
Bug21651 - Prolog ?? and reasoning
On a reasoning triple store, the prolog ?? construct in the predictate position used to fail with a type error. This bug has been fixed.
Bug21642: Agload buffer overflow
Due to a buffer overflow, agload could corrupt memory and potentially crash. This has been fixed.
Bug21640: Race condition when reaping abandoned sessions
Previously, if concurrent processes performed the operation to reap abandoned sessions, shared memory state could be corrupted, resulting in hangs or crashes. This has been fixed. (This bug was actually fixed in version 4.10.)
Bug21625 - Large result sets could produce bogus triples with INSERT and CONSTRUCT
In cases where there were more than 100,000 results, the machinery that prevents INSERT and CONSTRUCT queries from producing duplicate results could create invalid answers. This has been corrected.
Bug21596 - Serialize-rdf/xml could fail on some predicates
AllegroGraph's RDF/XML serializer would fail if a predicate ended with something other than a letter, a digit, an underscore or a dash. This conformed to an older version of the Extensible Markup Language but not to the most recent version. This has been corrected.
Bug21586 - Possible divide by zero error in index optimizer
Under some circumstances an index optimizer could attempt to perform a division by zero when logging statistics to agraph.log. This would result in a non-fatal error message being logged instead of the statistics. This has been corrected.
Bug21580 - Improve external variable binding bookkeeping
The values for externally supplied variables could be lost for some complex interactions of EXISTS (or NOT EXISTS) filters and UNIONS.
This has been corrected.
Bug21570 - Fix 'No session ports available' error message
When trying to start a dedicated session and no more free ports were available, AllegroGraph failed with an internal error (calling @UUID on NIL) instead of producing an informative error message. This bug has been fixed.
Also, the http error code was changed from 400 ("Bad request") to 503 ("Service unavailable") to indicate a temporary condition.
Bug21553 - Fix MemoryCheckWhen without MemoryReleaseThreshold
If the memoryReleaseThreshold configuration directive was not specified but memoryCheckWhen was, then query execution failed with type errors trying to compare memory footprint to NIL. With this fix, AllegroGraph refuses to start in these circumstances.
HTTP Client
Rfe12136 - Optimize front-end http server
The timeout for reading headers was lowered to 5s which makes the front-end http server make better use of its available resources and more resilent when clients with http keep-alive don't close the connection in a timely manner.
Also, a warning is logged if the number of idle http worker threads falls below 2, because it can easily cause a performance drop.
Rfe12296 - Support AllegroGraph direct reification in SPARQL
AllegroGraph now supports direct reification in SPARQL queries using the <http://franz.com/ns/allegrograph/4.0/tripleId> magic property. This property allows you to bind the ID of a triple to a SPARQL variable which can then be used in reification. For example, the following query first adds two triples and then adds four additional triples that describe the first two:
prefix : <eh://>
prefix franz: <http://franz.com/ns/allegrograph/4.0/>
insert data {
:gary :likes :dogs .
:gary :likes :cats .
} ;
insert {
?id :mentioned ?now .
:gary :believes ?id .
} where {
?id franz:tripleId (:gary :likes ?what) .
bind( now() as ?now )
See the documentation for additional details on direct reification and its advantages and limitations.
Rfe12246: Enhancements to SPARQL freetext queries
The fti:match
and fti:matchExpression
predicates can now optionally retrieve the object of the matching triples and select the freetext index to use. (These enhancements are currently available only for AllegroGraph's native freetext indexes. Support for Solr and MongoDB will be forthcoming).
The new features rely on SPARQL magic properties to provide a syntactic shortcut for list patterns. As an example, this query retrieves the subject (into ?subject) and text (into ?text) for the freetext query that matches "nepal":
select ?subject ?text {
(?subject ?text) fti:match 'nepal' .
This query retrieves only subjects and uses only the freetext index named comments
select ?item {
?item fti:match ('upgrade' 'comments')
More examples and information can be found in the documentation.
Rfe12243 - Support AllegroGraph Social Networking Analysis in SPARQL
AllegroGraph's SPARQL engine now supports a set of magic properties to enable Social Networking Analysis including centrality measures, path finding and cliques. See the documentation for more details.
Rfe12231 - Improve SPARQL geospatial integration
AllegroGraph now supports several magic properties to make SPARQL / geospatial integration easier. For example, this query finds all of the points within a circle centered at 10, 2:
select ?who ?where {
(?who ?where) geo:inCircleXY ( ex:location 10 2) .
The following magic properties are provided:
(where geo
is the usual Geospatial namespace abbreviation for <http://franz.com/ns/allegrograph/3.0/geospatial/>). See the documentation for additional details on using these properties.
Rfe12171 - Improve variable GRAPH clause handling in some situations
SPARQL specifies that a graph clause like
GRAPH ?g { ... }
must be implemented as if it iterated over each graph in the dataset and took the union of the resulting bindings. There are sometimes more efficient ways to get the same results and AllegroGraph uses these when it can. AllegroGraph was not, however, using information about any constraints on the variable ?g
that were provided by other parts of the query. For example, a query like:
?s :p ?g .
GRAPH ?g { ... }
might produce a single binding for ?g
but AllegroGraph was still iterating over all of the named graphs of the dataset. This has been optimized so that AllegroGraph will use the additional information when it can determine that the number of bindings for ?g
are smaller than the number of graphs in the dataset.
Rfe12057 - Manage disk and memory resources better for CONSTRUCT queries
When there are many results, SPARQL CONSTRUCT queries buffer their results to disk to conserve memory. The cutoff value for when to buffer to disk was unnecessarily small which meant that CONSTRUCT went to disk more often then necessary. This has been corrected.
Rfe12035 - Improve handling of some SPARQL queries with a GRAPH clause
By definition, SPARQL must handle a GRAPH clause as if the query engine evaluated the clause once for each graph in the dataset. However, it is often possible to evaluate the clause more efficiently.
This change improves the heuristics AllegroGraph uses to determine when the more efficient approach will achieve the correct results which means that some queries with a GRAPH clause will be executed more quickly.
Rfe11319 - Support SPARQL federated queries (the SERVICE clause)
AllegroGraph now supports SPARQL federated query using the SERVICE clause. The initial implementation is functional but not highly optimized.
Rfe8063 - Support AllegroGraph temporal reasoning in SPARQL
AllegroGraph's SPARQL engine now supports a set of magic properties to enable temporal reasoning. See the documentation for more details.
Bug21757 - SPARQL geospatial queries could fail
Depending on the set up of a triple-store's geospatial subtype mappings, it was possible for a SPARQL query using geospatial extensions to fail to find results. This has been corrected.
Bug21742 - SPARQL parser failed on quad patterns with collections
The SPARQL parser could lose track of triple-patterns that arose from abbreviations using either nested blank nodes or collections. This has been corrected.
Bug21725 - Correct potential error when SPARQL Update touches too many rows
If a SPARQL DELETE ... INSERT ... WHERE
request changes many rows, then AllegroGraph caches the results of the WHERE expression to disk to reduce memory pressure. In some cases, this could result in a error when the cached results were re-read. This only occurred for Update requests that touched more than 100,000 rows. This has been corrected.
Bug21718 - Unused variable optimization could produce incorrect results
AllegroGraph analyzes SPARQL queries that use DISTINCT in order to remove the collection of bindings for variables that are not needed to produce the final result. In some cases, it was possible for this analysis to cause the execution of a code path that added solutions incorrectly. This has been corrected.
Bug21573 - SPARQL queries could intern strings unnecessarily
SPARQL queries that used the FROM or FROM NAMED clause always tried to intern the graphs into the triple-store's string table. This was both unnecessary and could cause an error if the triple-store was read-only or a federation.
This has been corrected.
Bug21011, Bug21571 - handle nested SPARQL BGP syntactic sugar correctly
Some SPARQL triple-patterns that involved nested brackets and object lists were being parsed incorrectly. This has been corrected. Some examples of queries that work correctly now but that failed without this change include:
PREFIX : <ex:>
:x :y [:z (:b [:d (:e :f),(:g :h)])]
PREFIX : <ex:>
?psi :a :b, [:c :d], [:e :f] .
PREFIX : <ex:>
?psi :a :b, [:c [:d :e]] .
Improve Pattern estimation where there is no :p index
Improved query pattern estimators for triple-stores with no predicate index (e.g., :posgi, :psogi, etc.). This will help re-order query clauses more intelligently.
Rfe12325 - Add audit log query interface to AGWebView
There is now an audit menu item in the admin menu. This provides access to the audit log query page which lets you filter audit log events by user, class and date.
Changes to the Lisp API
Bug21708 - Fix some low-level Lisp API geospatial functions
Some low-level Lisp API functions had not been enhanced to account for AllegroGraph's geospatial encoding. This has been corrected.
Bug21689 - Lisp client printer variable leakage
On a remote store, the run-sparql function failed with an 'Illegal sharp character' error if print-length was set to a small value. This bug and more generally the leakage of printer variables into run-sparql has been fixed.
No significant changes.
Python Client
No significant changes.
Java Client
Rfe12118 - AGRepository with connection pooling
With this change, an AGRepository can now be configured to use a connection pool via the setConnPool method, enabling Sesame apps to transparently benefit from connection pooling. See the javadoc for setConnPool for details.
Rfe10513 - Configurable blankNodesPerRequest
With this change, the Java client supports configuring the number of blank nodes automatically fetched per request to the server by the AGRepository's AGValueFactory. The default remains at 100, but it can be configured by setting the property:
Applications can also configure it directly, see the javadoc for AGValueFactory#setBlankNodesPerRequest for details.
Rfe9869: Support SPARQL/Update from Jena
With this change the Jena adapter supports an execUpdate method in AGQueryExecution for executing SPARQL Updates. Jena Tutorial example13 has been augmented to demonstrate its use.
AllegroGraph 4.10 user-visible changes
AllegroGraph Server: General Changes
Rfe12004 - Ag4 plugins for TBC 4.0.0
With this change, the AG plugins have been updated to work with TBC 4.0.0. For installation details, see Top Braid Composer Plugin.
Rfe11986 - Improve efficiency of some property path queries
AllegroGraph now evaluates property path queries whose initial or final endpoints come from a small set of values more efficiently. For example, a query like
prefix gnO:<http://www.geonames.org/ontology#>
select ?id ?par ?parname {
bind (URI('http://sws.geonames.org/104515/') as ?id)
?id rdf:type gnO:Feature .
?id gnO:parentFeature+ ?par .
optional {
?par gnO:name ?parname
will be evaluated much more quickly than before because the subject of the path query is fixed.
Rfe11937: Agload: remove blank node cache size guessing code
In agload, blank node cache size guessing code did not work very well. It was removed and the blank node cache size defaults to 1,000,000 which works reasonably well on small and large memory machines.
This change will only be noticed when loading ntriple or nquad files with blank nodes.
Rfe11839 - Improve eager evaluation of impossible query constraints
AllegroGraph tries to evaluate FILTER constraints as early as possible. In particular, a constraint may become impossible or a tautology before the query even runs if external variable bindings are supplied. AllegroGraph was already handling tautologies eagerly but was not doing the same for impossible constraints. This has now been remedied.
Rfe11827 - Improved memory footprint of joins with unbound variables
Previously, queries involving joins had a worst case memory footprint of O(2^N) where N is the number of join variables. This is now O(1), but the time complexity is O(N). In practice, this means that the client gets a timeout instead of a memory exhaustion warning.
Rfe11233 - Simplify property path queries when possible
Property path queries that do not use the zero or more
or one or more
operators and that do not have complex alternation can be expanded directly into simpler forms. This lets them be executed using the regular query machinery which can often be faster than the specialized path query machinery.
Rfe9699 - Dynamically grow string table files
Prior to this change string tables files were large sparse files. The apparent size of these files frequently led to user confusion. In addition, full filesystem errors were not handled gracefully when modifying the sparse files. Now string table files start at a minimum size and grow as needed. If growth of a string table fails due to a full filesystem error, a complaint will be logged to agraph.log and the operation will be retried periodically until it succeeds.
Bug21592: Improve cursor resource management
Some cursors were failing to close all of their file handles which could lead to errors. This has been corrected.
Bug21583 - see Bug21575 below.
Bug21582 - Complex nested unions could fail to return some bindings
Given the right data, a complex query involving multiple nested unions could misapply an optimization meant for one part of the union to a different part. This could lead to some variables in the query being unbound.
This has been corrected.
Bug21575, Bug21583 - property path optimizations and better bookkeeping
Improve the way that AllegroGraph implements some property path queries.
Correct a problem with property path queries and over-zealous resource management.
Improve the bookkeeping of unused variables when using external bindings.
Bug21570 - Fix 'No session ports available' error message
When trying to start a dedicated session and no more free ports were available, AllegroGraph failed with an internal error (calling @UUID on NIL) instead of producing an informative error message. This bug has been fixed.
Bug21550 - Complex FILTER EXISTS expressions could cause parsing errors
Complex FILTERs that used EXISTS (or NOT EXISTS) could signal errors during parsing. This has been corrected.
Bug21549 - Nested sub-queries could fail to project variables correctly
A query with nested sub-queries that used *
to return all variables in some of the sub-queries could incorrectly reason about variable scope which could cause queries to fail. This has been corrected.
Bug21534 - Garbled error message on memoryCheckWhen parsing failure
When the memoryCheckWhen configuration directive had an unsyntactic value ("memoryCheckWhen junk:1"), the error message was wrong. This bug has been fixed.
Bug21506 - Correct possible error when mixing UNION and GRAPH
Under some circumstances, a query with both UNION and GRAPH clauses could signal an error during execution. This has been corrected.
Bug21505 - Unused variables from a sub-query could confuse AllegroGraph
AllegroGraph removes query variables that are not used if a query has either the DISTINCT or REDUCED modifiers. The unused variables logic was not correctly handling the case of a sub-query whose projected variables were not used elsewhere. This could lead to an error during query processing. This has been corrected.
Bug21498: Do not signal error when all ORDER BY expressions are redundant
AllegroGraph removes ORDER BY expressions that do not depend on the bindings of a row because they cannot have any bearing on the outcome. For example, the query:
SELECT * { ?s a ?o } ORDER BY ?pineapple
is equivalent to the query
SELECT * { ?s a ?o }
Unfortunately, AllegroGraph was incorrectly signaling an error when all of the expressions in an ORDER BY clause were irrelevant and therefore removed.
This has been corrected.
Bug21497 - Filters could be misapplied in some situations
AllegroGraph attempts to move FILTERS closer to where they apply in order to increase query speed. If a FILTER was applicable on both sides of a UNION and also applied to single triple-patterns then it was possible for AllegroGraph to think that the FILTER only needed to be used on the left-hand side of the UNION. For example, a query like this could fail to apply the FILTER to ?c
on the right-hand side:
select * {
{ ?a ex:b ?c . } union { ?a ex:c ?c . }
filter (?c*2 = 2)
This has been corrected.
Bug21496 - Improve memory management for CONSTRUCT queries
AllegroGraph now tracks memory more accurately and manages it more efficiently for CONSTRUCT queries.
Bug21493 - Bind is too aggressive in assuming single values
AllegroGraph was over-optimizing assignment (BIND) such that assignments to the same variable name in different pieces of a UNION could fail to work correctly. For example, a query like
{ BIND( :person1 as ?person ) }
{ BIND( :person2 as ?person ) }
would return only one binding for ?person rather than two.
This has been corrected.
Bug21486 - Correct handling of some IN LINE data syntax
AllegroGraph was not correctly reading all of the supplied values when using the abbreviated simple-variable syntax. E.g., a query like
select ?person (concat(?first, ' ', ?last) as ?name) {
values ?person { ex:person1 ex:person2 ex:person10 }
?person ex:first-name ?first .
?person ex:last-name ?last .
was processing only the first supplied value. This has been corrected.
Bug21476 - Some blank nodes could fail to print in a 32-bit Lisp client
It was possible for blank-nodes to raise an error when AllegroGraph tried to print them in N-Triples format. This has been corrected.
Bug21470 - Corrected Turtle parser relative URI normalization
AllegroGraph was incorrectly applying sections 6.2.2 and 6.2.3 of RFC3986 when it merged a base URI with a relative one. This has been corrected.
Bug21458 - Standardize AllegroGraph exit code
AllegroGraph's license check can be resolved in three ways:
Normal start up - a license is present and correct.
Free start up - no license is present so the free limit is used.
Limited start up - only partial license information is present so AllegroGraph runs in free mode.
In all of these cases, the exit code returned will be zero (0).
If the license code is invalid or if there are any other problems with server start up, then AllegroGraph will fail to start and return a non-zero exit code.
Bug21454 - URI parsing was too strict
AllegroGraph was being stricter than necessary when parsing BASE URIs such as foo:bar:/baz
. This has been corrected.
Bug21379 - Reasoning triple-store confusion about unspecified graph fixed
A reasoning triple-store failed to distinguish between a query where the graph was left off (i.e., left as a wild card) and a query where the graph was explicitly set to the default-graph of the current triple-store. This could cause it to infer incorrect triples.
This has been corrected.
Bug21365 - Fix lookup of user access rights when authorizing access to repositories in the root catalog.
AllegroGraph would deny authorization requests on repositories in the root catalog under some conditions, despite specific user access right allowing such (read/write access on catalog "/", repository ""), or global rights (read/write access on catalog "", repository "*"). This has been corrected.
Bug21353 - Correctly handle aggregation on empty datasets
AllegroGraph was failing the Data Access Working Group (DAWG) "agg empty group" test because it was not returning a row for a query asking for aggregation on an empty dataset. This has been corrected.
Bug21158 - Catch errors during filter analysis
AllegroGraph was signaling an error during query planning if the eager analysis of a FILTER expression resulted in a error. The correct behavior is to treat the FILTER as an impossible constraint.
This is now handled correctly.
HTTP Client
Rfe11609 - Support text/table content-type in the HTTP protocol
AllegroGraph will now return a simple ASCII table if an HTTP request uses the content-type text/table
. For example, a query might return a table like:
| person | name | location |
| mo:Bob | "Bob" | --- |
| mo:Robert | "Robert" | 23 |
Bug20622: "Mode" was not optional for DELETE /statements/duplicates
The mode parameter, which is used to indicate which components of each triple must be equivalent to count as duplicates of each other, is now optional and defaults to "spog" for the DELETE /repositories/[name]/statements/duplicates HTTP protocol request.
Rfe11920 - Signal error when aggregate expressions are used in the wrong place
AllegroGraph did not signal a useful error when aggregate expressions were used incorrectly in a SPARQL query. E.g.,
?a ex:foo ?value .
BIND( SUM(?value) AS ?sumValue )
This has been corrected.
Rfe11494 - Update semantics of SPARQL property path queries
AllegroGraph's property path queries now match the updated semantics of the SPARQL 1.1 specification. In particular, wild-card operators like *
and +
no longer count their matches. AllegroGraph still supports the now deprecated counting operations, e.g.,
but no longer counts the unique paths found. I.e., you can use these non-standard operators to find if there is a path but not to count the number of paths.
Note that AllegroGraph now passes all of the Data Access Working Group (DAWG) tests with the exception of
(pp37) Nested (*)*
This test uses the path
and AllegroGraph incorrectly returns some duplicate results.
Bug21599 - Variable GRAPH queries that used the graph could lose results
A SPARQL GRAPH query that used a variable graph and included the graph variable in the body of the query could under some circumstances lose results. For example, a query like
GRAPH ?g {
?g a <FoodGroup> .
?g <covers> ?r .
could possibly have returned too few results depending on the data in the store.
This has been corrected.
Bug21581 - Improve bookkeeping when using property paths
If AllegroGraph can determine that a variable in a SPARQL query is not used, then it will enable certain optimizations. For example, if a query is returning DISTINCT results and a variable is not used in any joins nor returned by the query, then its values do not matter.
This logic was not correctly rewriting property paths to account for the unused varaibles.
This has been corrected.
Bug21562: Insert & remove-graph-uri(s) should not override WITH
If insert-graph-uri(s) or remove-graph-uri(s) were passed as query parameters to a SPARQL DELETE...INSERT...WHERE statement, then AllegroGraph was using these parameters even if the statement used WITH to specify a GRAPH. This is now corrected. SPARQL Update statements that use WITH will not be overridden via insert or remove graph URI(s).
Bug21551 - Deletes via SPARQL Update did not correctly handle encoded UPIs
SPARQL DELETE DATA and DELETE...INSERT...WHERE commands could fail to remove some triples due to AllegroGraph's internal representation of typed literals. The failure would occur only if the literal was specified directly (i.e., when the literal was a variable, AllegroGraph behaved correctly).
Bug21548 - Nested unions with fixed patterns could miss results
If a SPARQL query contained nested unions and these unions contained fixed triple-patterns (i.e., patterns with no variables or patterns where all of the variables are bound via some external binding), then some results from these unions could be lost. This has been corrected.
Bug21546 - Correct off-by-one error in some SPARQL constraints
Depending on the data and the query, some SPARQL constraint analysis could lead to a range error. This has been corrected.
Bug21515 - Improve SPARQL parser speed
Compliance changes in the SPARQL parser of AllegroGraph v4.9 reduced the speed of parsing significantly for very large queries and update requests.
This has been corrected so that parse speed is now equivalent to what it was in AllegroGraph v4.8.
Bug21514 - Fix possible error caused by nested sub-query
The data structures used for SPARQL sub-queries were sometimes being cleaned up too early which could lead to a bus error. This has been corrected.
Bug21507 - Fix problem with property path query clause estimation
AllegroGraph was incorrectly estimating the size of clauses involving property paths in SPARQL queries which could lead to poor plans. This has been corrected.
Bug21478: Fix spurious parsing error when mixing sub-query and aggregation
AllegroGraph's SPARQL parser could become confused if a query mixed sub-query and aggregation and the sub-query used *
to refer to all variables.
This has been corrected.
Bug21469 - Relative URIs were not being correctly normalized by the SPARQL parser
Section 5.2 of RFC3986 specifies how "." and ".." path components of relative URIs should be normalized when merging with a BASE URI. The original SPARQL parser implementation skipped this step in the interests of efficiency. This has now been corrected.
Bug21464: Some combinations of nested UNION and OPTIONAL could fail
The SPARQL 1.1 engine could fail to correctly keep track of solution bindings for queries with certain patterns of UNIONs and OPTIONALs. This has been corrected. #### Bug21501 - Queries with cross-products and empty RHS could emit incorrect solutions
If a query had a cross-product and the right-hand side of the cross-product was empty, then it was possible for AllegroGraph to not discard the solutions on the left-hand side. This has been corrected.
No significant changes.
Changes to the Lisp API
Bug21535 - Db registry memory leak in the Lisp client
If a triple store object isn't closed properly and becomes garbage, the finalizer is supposed to close it. Fixed a bug that rendered this mechanism ineffective, causing leakage of memory.
Bug21512 - With-variables not handled consistently with sub-queries
In some cases, external bindings imposed from with-variables
could be lost when using sub-queries. This has been corrected.
No significant changes.
Python Client
No significant changes.
Java Client
Rfe11527: Support sessions that use the main server port
With this change, the Java client can now be configured to have sessions use the main server port rather than a dedicated port. By default, a dedicated port will be used. Setting the system property com.franz.agraph.http.useMainPortForSessions=true will configure the client to use the main port for sessions.
Rfe8384: Limiting the duration of a query
With this change, the Java client now supports limiting the duration of a query. When Sesame applications use the AGQuery#setMaxQueryTime method, the AG server will timeout the query appropriately during evaluation and clean up server resources, and the client library will throw a QueryInterruptedException back to the client application.
AllegroGraph 4.9 user-visible changes
AllegroGraph Server: General Changes
Rfe11922 - Add materiazer. See Materializer for details.
Rfe11879 - Improve error message on invalid license
AllegroGraph now prints information to the console when there are problems with the license settings in the configuration file.
For example, if the configuration file is missing the LicenseExpires
parameter, then AllegroGraph will print:
AllegroGraph Server Edition 4.9, built on October 01, 2012 10:04:33 GMT-0700
Copyright (c) 2005-2012 Franz Inc. All Rights Reserved.
current-time: Monday, October 01, 2012 10:43:09 AM
Server started: LicenseExpires parameter missing. Running with triple-limit of 5,000,000.
Rfe11845 - Optimize blank node printing
Blank nodes now print slightly faster and more efficiently than they did before.
Rfe11827 - Reduce memory footprint a bit
Result arrays are now freed right when they become unused. Previously, garbage accumulated until a certain limit was reached. This should have a small positive effect on high water-mark memory footprint.
Rfe11784: Release memory back to the operating system after query failure
Prior to this change, AllegroGraph would continue to claim memory used for queries even after the query would complete. AllegroGraph will now return unused memory back to the OS when a query memory failure occurs.
Rfe11762: Improve the efficiency of queries with unbound results
Queries that use UNION or OPTIONAL can have unbound columns in the result set. This change improves the way AllegroGraph does joins when there are unbound columns in a result set.
Rfe11756: Improve the chunk processing behavior of ORDER BY and LIMIT queries
The chunk-at-a-time processor automatically reduces the size of the chunks being processed based on the limit (it makes no sense to process a chunk of 500,000 rows if you are only interested in the first one!). In the case of ORDER BY queries, however, it makes sense to keep the larger limit since all of the results must be examined. This is now the case.
Rfe11728: Improve handling of large DISTINCT or ORDERed results
This enhancement improves the efficiency of the on-disk merging operations so that the size of ORDERed or DISTINCT result sets is limited only by disk space and not by available RAM.
Bug21531 - Non-simple EXISTS FILTERs could cause query failure
AllegroGraph was incorrectly processing non-simple graph patterns in an EXISTS or NOT EXISTS FILTER. This meant that queries like
could cause an error rather than being correctly processing. This has been corrected.
Bug21415 - Queries could return invalid solutions
It was possible for solutions with no bindings for some of their variables to escape from the right-hand side of a join. This would cause too many solutions to be returned from the query.
This has been corrected.
Bug21410 - Duplicate suppression not handling deleted triples correctly
AllegroGraph was handling deleted triples improperly when duplicate suppression was enabled. This has been corrected.
Bug21407 - An error in a SELECT expression prevented processing of subsequent ones
An error in a SELECT expression would prevent processing of the rest the expressions in the query for the current solution. For example, depending on the data, in a query like:
(STRAFTER(?str,"b"@cy) AS ?abcy) # could cause a type error
(STRAFTER(?str,"ab") AS ?aab)
?s :str ?str
The evaluation of STRAFTER()
with a second argument of "b"@cy could signal a type-error. AllegroGraph was stopping further computation at that point which meant that the binding for ?aab
could be left empty when it should not have been.
This has been corrected: now, each expression is computed separately.
Bug21404 - Config file EOL format
Previously, non-unix newlines (CR+LF, LF+CR) in the license section of the config file could prevent the server from starting up. This has been fixed and any mix of Unix, Mac and DOS style newlines is accepted.
Bug21398 - Variables in EXISTS filter could be incorrectly bound
It was possible for variables that appeared only in an EXISTS (or NOT EXISTS) filter to be incorrectly bound during query evaluation which could lead to incorrect results.
This has been corrected.
Bug21390: N-Triples serializer does not handle embedded angle brackets
Even though valid URIs are not allowed to contain embedded angle brackets, it is still possible to add them to a triple-store. For example, the valid N-Triples file:
<ex://h> <ex://p> <ex://invalid\u003E>
would add a triple whose object is ex://invalid>
AllegroGraph was serializing such URIs without performing the necessary \u escaping which meant that the data exported could not be re-read by AllegroGraph's parsers.
This has been corrected.
Note that this was only a problem for data with invalid URIs.
Bug21377 - Updates with both DELETE and INSERT
Due to a race condition in a shared backends, updates that involved both DELETE and INSERT could produce bogus results. This bug has been fixed.
Bug21376 - Wrong results with ORDER BY
Due to a rare race, in shared backends, queries with ORDER BY could produce bogus results. This has been fixed.
Bug21367 - Expressions in ORDER BY could cause query failure
Queries with expressions in an ORDER BY could cause query failure during string look up. This bug was introduced in AllegroGraph v4.8 and is now corrected.
Bug21349 - Eager evaluation of boolean FILTERS could lead to failures
If a query used FILTERS consisting of boolean combinations of simpler filters and also used external variable bindings such that some of the FILTER clauses could be evaluated immediately, then it was possible for the FILTER evaluator to signal an error.
This has been corrected.
Note that bug21342 corrected this problem for the simpler case of negation. This bug fixes the more general case.
Bug21345 - Possible problem with BIND inside of an OPTIONAL
If a query included a BIND clause that stood by itself and there was a join, it was possible to lose the value of the binding. In particular, a query like
SELECT * { ?a ?b ?c . OPTIONAL { bind('hello' as ?x } }
could leave ?x
unbound. This has been corrected.
Bug21344 - Bind could fail to use external variable bindings
If a query used the BIND form and the value of the expression depended on variables set via an external binding (e.g., via the with-variables
argument in the Lisp API or via HTTP parameters in the HTTP interface), then it was possible for the BIND expression to ignore those values. This has been corrected.
Bug21342 - Eager evaluation in FILTERs can lead to problems using variables
If a query uses a FILTER and also variable bindings such that an expression in the FILTER could be evaluated before actually running the query and if the expression was used in other boolean combinations (e.g., with not
, and
, or or
), then it was possible for AllegroGraph to signal an error. For example, if the query was
select * { ?a ?b ?c . FILTER( ! bound( ?d )) }
and if ?d
was bound using a variable binding, then AllegroGraph would signal an error instead of correctly realizing that the FILTER could never succeed.
This has been corrected.
Bug21341 - Non-simple IF statements could cause an error
It was possible for non-simple IF statements in an expression to lose track of their variables which led to an error at query planning time.
This has been corrected.
Bug21326 - Geospatial query failure
Fixed a bug that, under rare circumstances, caused geospatial queries to fail with bus error.
Bug21325 - Lost results in sub-queries and some joins
When an internal buffer holding intermediate results was grown in a sub-query or in some joins, results could have been lost. This bug has been fixed.
Bug21272 - No results with BIND
Sometimes, as in the query below, instead of no results, a single result was returned when BIND was involved.
select * {
bind('o' as ?c)
?a ?b ?c .
?d ?e ?f .
filter( ?a < ?d && ?d < ?a )
This bug has been fixed.
Bug21270 - Sub-queries with ORDER BY can fail to bind results
Depending on the data and what other queries have been evaluated, a query that used an ORDER BY clause in a sub-query could fail to correctly bind the result variables. For example, a query like:
select ?age {
{ select ?age {
?who <http://people.example/age> ?age .
} order by ?age
could return results but leave the bindings for ?age
This has been corrected.
Bug21260: Xpath Constructor Functions fail on strings to numbers
The XPath Constructor Functions should convert typed string literals into the requested numeric type when the value of the string can be so coerced. For example:
xs:int('2'^^xsd:string) ==> 2
AllegroGraph was raising a type error in this case. This has been corrected.
Bug21256: Parser problem with some queries that mixed aggregation and sub-query
AllegroGraph was incorrectly signaling a parser error on some queries that mixed aggregation and sub-query. For example,
select (max(?a) as ?foo) {
select distinct ?a ?b {
?a a ?c .
?c a ?b .
This has been corrected.
Bug21245: Allegrograph's turtle parser performs URI normalization incorrectly
Percent encoded URIs should not be unescaped when loading data in the Turtle format. AllegroGraph was incorrectly doing so. This has been corrected.
Bug21243 - Non-QNameable URIs cause turtle serializer error
If a triple contained a URI that could not be expressed as a QName, then the turtle serializer would signal an error that it could not split the URI rather than just emitting the entire URI and continuing. For example, a triple containing the URI <<ttp://example/> would cause this error:
Cannot split <http://example/> into XML QName.
This has been corrected.
Bug21226: Agload max blank node cache size not obeyed in all cases
Agload could over-allocate memory in a certain case. This has been fixed.
Bug21215 - Improve cursor resource usage of Prolog SELECT queries
AllegroGraph previously closed some of the cursors created while running a Prolog query lazily. It now closes them when the query completes which improves overall resource utilization.
Bug20906 - Remove duplicate triples fails on a store with zero triples
An error would be raised if duplicate deletion was attempted on a store with zero triples.
This has been corrected.
HTTP Client
Rfe11755 - Add support for insert-graph-uri, remove-graph-uri, etc.
Version 6 of the Sesame HTTP Protocol includes several graph parameters that can be used to control the behavior of SPARQL Update statements. These are:
remove-graph-uri - the graph from which triples are deleted in a DELETE/INSERT/WHERE clause.
insert-graph-uri - the graph into which triples are added in a DELETE/INSERT/WHERE clause
using-graph-uri and using-named-graph-uri - these specify the dataset (similar to using-graph-uri and named-graph-uri in the HTTP protocol and to the from and from-named keyword arguments in the Lisp API's
These four parameters are now supported by AllegroGraph
Rfe11743: Add baseURI to the SPARQL HTTP Protocol
The SPARQL HTTP protocol now accepts baseURI
as an HTTP query request parameter. This can be used to shorten the rest of a SPARQL query.
Bug21408 - Retrieving JSON statements over HTTP
Fixed a bug that caused the statement list to be truncated when an 'application/json' encoded response was requested via the HTTP protocol.
Bug21280 - Query failures cause spurious errors
AllegroGraph 4.8 modified the internal API used to signal query failures (e.g., due to timeout or memory limits). Unfortunately, the code in the HTTP layer of AllegroGraph was not modified to accommodate the change which led to spurious bus errors when a query failed. This has been corrected.
Rfe11862 - Match default dataset behavior for SPARQL Update and Query
SPARQL Update was using a default dataset that contained only triples with unnamed graphs (the default graph in AllegroGraph terminology) in the FROM portion and put triples with graphs into each of their graphs in the FROM NAMED. This was different from the default dataset for SPARQL Query which put all of the triples into the FROM portion and treated the FROM NAMED portion similarly.
AllegroGraph now uses the same default dataset behavior for both Query and Update. This dataset is as described for query above. Note that this means that an Update command like
DELETE DATA { <eh://a> <eh://b> <eh://c> }
will delete the triples
{ <eh://a> <eh://b> <eh://c> }
from every graph in which it appears whereas the previous behavior would have been to delete it only from the default graph.
Note that triples added during an Update command which do not specify a graph will be added to the triple-store's default graph.
Rfe11817 - SPARQL parser should signal an error on badly formed requests
Previously, the SPARQL parser would silently accept nonsense queries like:
<http://www.foo.com> <http://www.bar.com> 'banana' .
because it would silently ignore tokens that came before the SPARQL prologue (i.e., before PREFIX and BASE) and convert such a query into an empty UPDATE request (i.e., a non-operation).
These queries will now signal a SPARQL parse error. Because the parser is now more strict, some queries that previously parsed may now signal an error. For example, this invalid query was previously accepted and now will not be:
# WRONG: bad prefix because it ends with a period (".")
PREFIX ex: <http://example.com> .
SELECT * { ?s ex:testsFor ?o . }
Rfe11793 - Improve handling of numeric and date literal equality filters
Improve the SPARQL 1.1 query planner's handling of numeric and date literal equality filters. In particular, AllegroGraph will now optimize queries with FILTER clauses like:
?s ex:p1 ?o .
FILTER( ?o = 3 )
which would previously have required a scan of all triples with predicate ex:p1.
Rfe11787 - Support SPARQL 1.1 UUID and STRUUID functions
Adds support for the SPARQL 1.1 UUID() and STRUUID() functions.
Rfe11779 - Support SPARQL 1.1 change to in-line data syntax
SPARQL 1.1 recently switched from a syntax for in-line data that used BINDINGS
to one that uses VALUES
. The standard also made it possible to use in-line data in more places. AllegroGraph now fully supports this feature and passes all of the Data Access Working Group (DAWG) tests for it.
Note that the BINDINGS syntax is still supported in this version of AllegroGraph. It will be deprecated and removed in some future release.
Rfe11757 - Provide select-N strategy for ordered results with small limit
Typically, a SPARQL query with an ORDER BY clause must accumulate all of the results before sorting them. If, however, the query has a small LIMIT, then it can be more efficient to retain the top LIMIT results and only sort those.
Rfe11555: Manage memory used to ensure unique results from CONSTRUCT and UPDATE
The data structures AllegroGraph uses to ensure that results of a SPARQL CONSTRUCT or UPDATE are unique have been modified so that result sets can be processed correctly regardless of size (up to the amount of available disk space).
Bug21401 - SPARQL Update must intern strings from variable bindings
If variable bindings are used in a SPARQL Update query and these bindings are part of the template being used to insert new triples into the store, then the strings from the variable values must be added to the triple-store's string table. This was not being done which could lead to a UPI not in string table error.
This has been corrected.
Bug21391 - Queries against in-memory-triple-stores could return incorrect results
The Lisp SPARQL API allows for the creation of in-memory-triple-stores from CONSTRUCT and DESCRIBE queries. These suffered from a bug such that queries that specified more than two of subject, predicate, object and graph fields could return incorrect triples. As examples, a query like:
ASK { ex:foo ex:bar ?o }
would work correctly whereas a query like
ASK { ex:foo ex:bar ex:baz }
could return yes
when it should have returned no
This has been corrected.
Bug21372 - Possible error when requesting sparql-xml
output for Prolog select
An error could be signaled if the default query engine was sparql-1.0
and a results format of sparql-xml
was requested for a Prolog select
This has been corrected.
Bug21371: IF confusion with free variables
SPARQL queries with free variables could produce incorrect results when using IF
. For example, the following query
SELECT ?result {
BIND( IF(!bound(?dataType), "first", "second") as ?result)
would return second
instead of first
. This occurred because the query engine was not correctly analyzing the free variable ?dataType
(this variable is free
because the query provides not binding for it).
This has been corrected.
Bug21361 - Improve SPARQL BASE URI handling
AllegroGraph was not always correctly merging base and relative URIs. For example, a query like
BASE <http://localhost:8080/>
SELECT * { ?a ?b </> }
was being incorrectly run as if it was
SELECT * { ?a ?b <http://localhost:8080//> }
This and other similar issues have been corrected.
Bug21357 - SPARQL blank-node parsing was too strict
The SPARQL parser was not allowing the full range of blank node names to be used. Thus, queries like:
?a ?b _:123 .
_:123 ?c _:fv-0 .
would fail to parse correctly. This has been corrected.
Bug21354 - Update STRAFTER() and STRBEFORE() to match changes in the standard
Recent changes to the SPARQL 1.1 standard changed the output of STRAFTER()
and STRBEFORE()
when no match is found. Previously, they were specified to return an empty literal with language or datatype that matched the first argument. Now they should produce an empty literal with neither language nor datatype. AllegroGraph now matches the standard.
Bug21294 - Sparql XML results for ASK queries missing head
The SPARQL XML generated by AllegroGraph was missing the <head/>
clause. Since this clause is generally empty, only systems that validate the results against an external DTD were effected by the missing clause.
This has been corrected.
Bug21277 - Improve cursor resource usage of SPARQL 1.1 queries
AllegroGraph previously closed some of the cursors created while running SPARQL 1.1 queries lazily. It now closes them when the query completes which improves overall resource utilization.
Bug21266: Queries with only a geospatial clause could fail to gather solutions
If a SPARQL query contained only a geospatial clause, then the SPARQL 1.1 engine could fail to add the solutions it found to the answer set. This has been corrected.
Bug21249: Incorrect return value of COPY GRAPH <X> TO GRAPH <X>
A SPARQL Update statement like
should have no effect on the triple-store and should succeed. AllegroGraph implemented the behavior correctly but was returning failure instead of success. This has been corrected.
Bug21239 - Concurrent queries in shared backends
With the sparql-1.1 engine, queries running in the same shared backend concurrently had unexpected interactions that lead to various errors. This has been fixed.
Bug21237: Computations in aggregate expressions could fail
If a complex expression was used inside of a SPARQL aggregation function, the value could be left unbound. A work-around was to express
(min(2 * ?x) as ?smallestDoubled)
(min(?x) as ?smallest) (2*?x as ?smallestDoubled)
This is now corrected and the work-around is no longer necessary.
Bug21233: SPIN functions could fail when used with constants
SPARQL queries that used SPIN functions could fail if the arguments to the functions were constants not already in a triple-store's string-table. This has been corrected.
Bug21222: Failing SPARQL UPDATE HTTP request should error
Previously SPARQL UPDATE requests that failed would return false
in SPARQL/XML format. In order to be better conform with other SPARQL endpoints, AllegroGraph now returns a 412 status code (precondition failed) instead.
Bug21163: Add new default-dataset-behavior: rdf
SPARQL leaves things up to the implementation when no explicit dataset is specified (i.e., when no FROM or FROM NAMED clauses are part of the query). AllegroGraph now provides three choices for dataset behavior:
- All triples will be in the FROM portion of the dataset. Triples with a non-default graph will be in that graph. Note that this means that triples with non-default graph slots will appear in the dataset twice: once in a named graph (named by their graph slot) and again in the default graph of the dataset.:default
- Only triples whose graph is the default graph of the triple-store will be in the default graph of the dataset. No triples will be in the named graph portion of the dataset.:rdf
- Only triples whose graph is the default graph of the triple-store will be in the default graph of the dataset. Triples with a non-default graph slots will be in the named graph portion of the dataset (each non-default graph triple will be in a graph named by the graph of that triple).
AllegroGraph's standard behavior continues to be :all. You can change this on a per-query basis using the defaultDatasetBehavior query option:
PREFIX franzOption_defaultDatasetBehavior: <franz:rdf>
Rfe11910 - Add HTTP handlers for materialization
Added the materializeEntailed service.
A PUT request will materialize entailed triples based on the with, without, useTypeSubproperty, and commit query parameters.
A DELETE request will remove the materialized triples.
Rfe11856 - WebView: new UI Beta for Graph
In WebView next to the Documentation menu is a link to "WebView Beta" a new experimental UI for Query and Graph. A link at the top will returns to the classic WebView.
A link at the top will open the new Graph View UI.
Also Node queries have a View menu in the results to open the node in Graph view.
Administration features of WebView are not yet included within the new UI.
Rfe11676: Webview: in Scripts editor, use CodeMirror JavaScript
The WebView Scripts editor now supports syntax highlighting and indentation by including the CodeMirror JavaScript mode.
rfe11596: WebView: new UI Beta for Query
In WebView next to the Documentation menu is a link to WebView Beta a new experimental User Interface (UI) for Query. The new UI provides a modern style and easier navigation. A link at the top will returns to the classic WebView.
All existing features of WebView Query are implemented:
- select repo
- query sparql
- query prolog
- free text search (pattern or expression)
- namespaces
- save and delete any of the above to user or repo areas
- recent queries
- example queries
- click node in results goes to new query screen
- download query results
- sessions (and functors)
Administration features of WebView are not yet included within the new UI.
Rfe11582: Webview: upgrade Query Editor to CodeMirror v2.32
The query editor for SPARQL and Prolog, implemented by CodeMirror, has been upgraded from v2.24 to v2.32.
Bug21250: Webview: remove limit from download
The download link for Query results no longer uses the limit parameter in the query UI.
Changes to the Lisp API
Rfe11454: get-triples-list
(Lisp API) returns cursor only on request
The Lisp get-triples-list
function previously returned the cursor it created as a second value. Now, however, it returns a cursor if either one was passed in initially (using the cursor
keyword argument) or if the new keyword argument return-cursor
is true.
Bug21381 - (Lisp API) SPARQL introspection functions required engine argument
The functions get-allowed-results-formats
and get-allowed-rdf-formats
returned nil
if no query engine was provided. This has been corrected.
Bug21378 - (Lisp API) sparql-1.1 engine does not implement destination-db
The Lisp API allows SPARQL Update commands to specify the triple-store that they modify. This feature was not included in the sparql-1.1 engine. This has been corrected.
No significant changes.
Python Client
Rfe11911: Add materializer calls to python client
Added materializeEntailed and deleteMaterialized calls to RepositoryConnection.
Java Client
Rfe11906 - Java support for the materializer
With this change, the Java client now supports materialization, allowing inferences to be generated and added to a repository in a transactional fashion. See the Javadoc for AGMaterializer#newInstance() to acquire a configurable materializer, and AGRepositoryConnection#materialize to run the materializer.
Rfe11771: Upgrade embedded JavaScript implementation
Fixes several small bugs in the way uploaded JavaScript scripts are interpreted. The most visible one was that the !== operator was acting like the < operator.
Rfe11241 - Support more query/update protocol params
With this change, the Java client now sends HTTP protocol params for update, baseURI, timeout, remove-graph-uri, insert-graph-uri, using-graph-uri, using-named-graph-uri, and logQuery.
AllegroGraph 4.8 user-visible changes
AllegroGraph Server: General Changes
Rfe11711 - Improve cursor resource usage of Geospatial Prolog queries
AllegroGraph previously closed cursors created while running a Prolog geospatial query lazily. It now closes them when the query completes which improves overall resource utilization.
Rfe11653 - Rm requests can be processed out of order
The order in which file management requests were processed caused unexpected errors under heavy load. The bug is now fixed.
Rfe11649 - Manage memory for ORDER BY and DISTINCT queries
Previously AllegroGraph needed to accumulate all results in memory for queries that used DISTINCT or ORDER BY. This could greatly increase the overall memory footprint. AllegroGraph now handles large result sets in available memory.
Rfe11631 - Improve query optimizer when inference is enabled
One part of query optimization is reordering the triple-patterns in each BGP. This reordering is based on the statistics collected by the store and these statistics do not take inference into account. This meant that the plan produced could be quite bad.
This has been corrected by modifying the estimation code to take RDFS++ into account.
Rfe11416 - Provide greater control of query memory usage
Added a memoryLimit
query option that controls how much memory a query can use. If a query needs to allocate more memory than this value, it will fail.
Bug21235 - Resource manager sync-files effectively ignores msync errors
If the filesystem on which a database resided filled up during a checkpoint, this fact was logged but the checkpoint process would continue running as if the error didn't happen, which would result in database corruption. This bug has been fixed. Now when a full filesystem is detected during a checkpoint, AllegroGraph stops operating in order to protect committed data.
Bug21224 - Crashes while processing queries with DISTINCT
Under rare circumstances, the internal data structures used while processing DISTINCT queries could get corrupted leading to segmentation faults. This bug has been fixed.
Bug21214 - Correct scope of BINDings introduced on the LHS of union
The binding of a variable on the left-hand side of a UNION should not influence its value on the right-hand side. For example, the following query should produce two rows with ?a
bound to 1 in one of them and left unbound in the other.
select ?a {
{ bind(1 as ?a) } union { bind(2 as ?b) }
AllegroGraph was retaining the binding on the LHS across to the RHS of the union and so was answering with two rows each of which had ?a
bound to 1. This has been corrected.
Bug21187 - Stack exhaustion with shared cursor
With lots of deleted triples a query could run out of stack when creating cursors. This has been fixed.
Bug21182 - Unbound values in distinct aggregrates could lose results
If a variable binding used in a distinct aggregate was unbound, it could cause other aggregrates in the same row to fail to update properly. For example, a query like:
SELECT (count( distinct ?taste) as ?tasteCount ) (count(?who) as ?whoCount) {
?who <http://people.example/age> ?age .
OPTIONAL { ?who <http://people.example/taste> ?taste . }
could lose data for the ?whoCount bindings if the ?taste binding from the OPTIONAL was unbound. This has been corrected.
Bug21145 - agload: message corrected for insufficient buffer size
The error message for insufficient ntriples/nquads buffer size was reporting buffer as size -1. This message has been corrected and now reports actual buffer size in order to abate confusion about the condition.
Note: This condition is usually triggered when an ntriple of greater than 4MB is encountered while using the default dispatch strategy.
Bug21136 - Free BGP patterns can lead to very large memory allocation requests
Queries with free patterns (like ?s ?p ?o) in a BGP on the right-hand side of a query could lead the query size estimator to believe that it should reserve a very large space to save the putative result set. For example, a query like
SELECT ?s WHERE {
{ ?s ?p ?o }
{ ?other ?p ?o . ?other ?someProp ?s }
would lead the query engine to try and allocate 1024-Petabytes. This has been corrected.
Bug21124 - Zero length path between non-matching constants
AllegroGraph was incorrectly finding a path between two different constants which led to queries like the following to return a single (empty) result when they should have returned no results at all.
select * {
ex:one ex:connectsTo{0} ex:two .
This has been corrected. Other zero-length path queries were behaving correctly.
Bug20853 - Updated the soundex algorithm
AllegroGraph's freetext indexing word filter was using an older variant of the Soundex algorithm that did not match the latest version (cf. http://www.archives.gov/research/census/soundex.html). The algorithm has now been updated.
Freetext indexes created with the soundex word-filter should be dropped and re-built.
HTTP Client
Rfe11681 - HTTP: Allow statements queries using the POST method
Add a [store]/statements/query URL that corresponds to /statements, except that it isn't limited to the GET method, and thus can be used to do complex queries without building up overlong URLs.
Rfe11680 - HTTP: Add /unique/[column] service
Add a [store]/unique/[column] URL that allows clients to fetch the set of unique parts that occur in a column in the database, optionally restricting other columns.
Rfe11682 - Improve performance of SPARQL OPTIONAL queries
If a query has the form A OPTIONAL B
(where A and B share variables so that it is a join) and the A part has no rows, then it is not necessary to evaluate the B part at all.
The SPARQL 1.1 query engine now recognizes this situation and skips the evaluation of the right-hand side.
Rfe11591 - Modified the Lisp run-sparql API to better handle query failure (e.g., for when a query runs out of time or other system resources).
Previously run-sparql
would return (as multiple values):
- the results of the query (or nil if the results were streamed)
- the verb of the query (e.g., :select or :construct)
- the list of variables
Now run-sparql
returns four values. In normal execution, the first three values are the same and the fourth value will be nil. When a query fails, the results will be:
- a keyword indicating why the query failed (e.g., :timeout)
- the verb
- the variables
- a property list of additional information (the properties will vary depending on the failure).
Code that requests a cursor should be prepared to handle a condition of type db.agraph.query.base:cancel-query-condition.
Rfe11581 - handle repeated Prologues in SPARQL UPDATE queries
SPARQL 1.1 UPDATE allows the Prologue (BASE and PREFIX definitions) to be repeated between each UPDATE command. Previously, AllegroGraph only allowed BASE and PREFIX to be used at the beginning of a SPARQL statement. This is now corrected.
Rfe11559 - Add logQuery parameter to the HTTP SPARQL protocol
SPARQL queries can now use the logQuery parameter in their HTTP requests. The parameter can be set to one of:
- false - no logging is reported
- true - log information is sent back in the body of the response (using text/plain).
- log - log information is added to the AllegroGraph log file.
The log output can be cryptic; please contact Franz Inc. for support in interpreting the messages.
Bug21220: SPARQL Update LOAD should require only write permission (not eval)
A user would need to have evaluate
permission on a triple-store in order to use SPARQL Update's LOAD command to load data from a file. This has been changed so that having write
permission is sufficient.
Bug21203 - SPARQL Update insert data fails to treat blank nodes correctly
The INSERT DATA and MODIFY SPARQL Update commands failed to use the small blank node identifier in the INSERT template. This caused multiple blank nodes to be created when there should have been only one.
Bug21192 - Upi not in string table error when mixing BIND, SPARQL Update and FTI
SPARQL Update queries that produced new strings (e.g., using BIND) on a triple-store with free-text indexing turned would lead to UPI not in string table errors. Note that in this case a triple would have been added to the store but its strings would not be added to the string table which could cause subsequent queries to fail until the errant triple was removed.
This has been corrected.
Bug21168 - Support SPARQL 1.1 COUNT(DISTINCT *)
The SPARQL 1.1 query engine was not correctly handling the COUNT(DISTINCT *)
form. This has been corrected.
No significant changes.
Changes to the Lisp API
No significant changes.
No significant changes.
Python Client
Rfe11697 - Added RepositoryConnection.prepareUpdate
Added RepositoryConnection.prepareUpdate for SPARQL 1.1 Update requests. The call to evaluate on the returned UpdateQuery object returns True or False.
Java Client
Rfe11748 - Upgrade to sesame 2.6.8
With this change, the Java client has been upgraded to use openrdf sesame 2.6.8 jars.
Rfe11243 - Support X.509 authentication
With this change, the Java client now supports X.509 server and client authentication. For set up details, see the javadoc for AGServer.
Bug21225 - With no requestEntity, post using setRequestBody
Previously, AGHTTPClient post method used setQueryString to pass params when there was no requestEntity provided. This burdened the server when a param became very large. Now params are passed using setRequestBody when no requestEntity has been provided.
See Change History for user-visible changes to earlier releases.


text:
by Quentin
Lady Gaga is moving aside on my iPod for bisexual British singer and songwriter Jessie J who said, "I've never denied it. Whoopie doo guys, yes, I've dated girls and I've dated boys—get over it."
I first heard her infectious hip hop track "Do It Like a Dude" in a hip hop class. The beats and lyrics were a blast to dance to… and I thought she was black. "Do It Like a Dude" has definitely inspired some neat combinations by hip hop dancers and choreographers. Continue reading


text:
Housewarming Gifts - Personalized Gifts
Gift Buzz
Specialty fruit baskets from Harry and David, Gourmet Gift Baskets and other top merchants are a classic and much-loved gift each Christmas. Look forward to the sweetest pears, golden apples and much more of unsurpassed quality and selection.... Read More »
Personalized gifts are one of the hottest trends this holiday season. Adding someone's name, initials or a special message is both timeless and totally on-trend. Ready to pick your perfect personalized gift? Check out our unique, thoughtful... Read More »
In general, men appreciate gifts that are more on the practical side. So when you are searching for an awesome housewarming gift for a man, look for things that he can actually use, but might not think to buy for himself. And don't forget... Read More »
All fall, people have been asking me one question: "What are the hottest gifts for the holidays?" I've been telling them the trends I'm seeing, including Uggs, succulents, tablet computers, and a whole category of gifts: personalized gifts.... Read More »
Hand-pickedHousewarming Gifts
The Gift Gurus at Gifts.com hand-pick all gift ideas in the housewarming category. View great personalized gifts ideas from the top stores online and further refine your results by price, Gift Guru top picks and more to find the perfect gift.


text:
Letters to the Editor
Read what our readers have to say about Maine.
Where in Maine?
Every month when my copy of Down East arrives, I turn to the mystery picture and take a guess. The May issue was the easiest ever. My grandfather bought a camp on Webb Lake about a hundred years ago and though I was raised in the Midwest, my family would journey to Weld for a few weeks each year. Climbing Tumbledown Mountain was a must. We always thought the pond on top was the crater of an extinct volcano. The granite outcroppings on the summit have wavy striations that look like molten lava after it hardened. The boulders we see in Webb Lake, and all around Weld, look like balls of lava that were shot out of the Tumbledown volcano — at least that was what we were convinced was the case (with my father's help). Today, geologists tell us that the boulders and the striations are the work of glaciers, but a few of us who have spent endless summers in Weld know the real story. Our annual trek up Tumbledown is to marvel at this "volcano," the bottomless core now filled with water.
—Don Smart
Damariscotta, Maine
In 1975, while attending Bangor Seminary, I became the student pastor at the Congregational Church in Weld, a position I held for two and a half years. In the late spring of 1975 I hiked up Tumbledown Mountain to see "Crater Pond." It was a hot day, so I stripped off my clothes, and jumped in to swim to the island. The water was really cold, so before swimming back, I laid on the rocks to warm up, and dozed off. When I awoke there were a number of women — a bird-watching group, a hiking group on an excursion, whatever — on the bank looking out to the island. All I could do was roll over and wait, hoping that none of them showed up in church the next morning!
—Rev. Dr. Alan Cutter
Baton Rouge, Louisiana
Back to the Beach
"The long curve of beach beckons into the distance." Thank you for the gem that is Kim Ridley's essay "Back to the Beach" in your May issue. Every sentence takes me back to early mornings and sunset evenings when light, color, smells, and sounds compelled me to the ocean's edge on a southern Maine beach. As I read, I waded with the author across, in my case, the mouth of a tidal brook, mindful of the tide's return. I always walked in the water, perhaps pausing on the jetty where all my senses absorbed the ocean, its life and creatures. Every word Kim Ridley wrote is eloquent and exactly right in truth and beauty — a treasure to keep. I am grateful to her and for the gifts of memorable summer mornings and evenings on the beach.
—June A. Knowles
Belmont, Massachusetts
Island Buffalo
In your May issue, the "My Maine" essay about discovering buffalo in Blue Hill Bay contained inaccurate information concerning the lands owned by the National Park Service (NPS). The essay said that Long Island within Blue Hill Bay was owned by the NPS and has been turned into a nature preserve. This is not true. The entire island is under private ownership. In 1995, the NPS purchased two conservation easements on the island. The easements are a type of land interest, but are not ownership of the land. The purpose of a conservation easement is to permanently conserve lands for future generations, while still being under private ownership for limited development use. The easements on Long Island allow for limited public access to a large portion of the undeveloped areas of the island. These easements also allow the NPS to manage and patrol, along with the owners, public use of lands. However, public access is not allowed on specific areas along the western shore (of which several are developed with homes or cabins).
Another small point of clarification: The conservation easements did require the bison to be relocated off the island in order to protect the natural resources from the bison. The family that brought the bison to the island removed all of them in 1997.
—Emily Seger Pagan
Land Resource Specialist
Bar Harbor, Maine
Whoopie War
I just opened the May issue and read the "Editor's Note." Who would have thought the humble, albeit delicious, whoopie pie would create a national sensation? I'm from Lancaster, Pennsylvania, the capital of Pennsylvania Dutch Country with the PA Dutch Visitors Bureau two miles from my home. (The state capital, Harrisburg, is in another county.) For at least fifty-nine of my sixty-one years, I've enjoyed whoopie pies from many of our local Amish bakers. Chocolate, oatmeal, pumpkin, chocolate chip, or sugar, they are all fantastic. I've also enjoyed Maine's whoopie pies while vacationing in Maine. To be honest, I can't say that one is better than the other. So I may be committing treason to my great state, but I honestly believe that if Maine wants the whoopie pie as the state snack, go for it! After all, we still have wet-bottomed shoofly pies!
—Suzanne Kresge
Lancaster, Pennsylvania
As a life-long resident of Pennsylvania (whose parents have lived in Woolwich, Maine, for the past eight years), I have taken a somewhat amused interest in the raging whoopie pie controversy between our two states. Although Pennsylvania may lay claim to this treat, I must admit that I have rarely seen these desserts outside of Lancaster County and the Pennsylvania Dutch area. In fact, the first whoopie pie I ever tasted was in Maine. I have visited Maine almost as long as I have lived in Pennsylvania and nowhere is it more popular than in Maine. Each year, my parents drive south for Christmas, bringing the whoopies with them for the family to enjoy. This Maine treat has definitely become part of our Pennsylvania traditions! Whether or not the whoopie originated in Pennsylvania is a moot point. There is no doubt that Maine has turned the whoopie pie into the widespread delight that it is today. So come on, Keystone State, lighten up and let Maine have the whoopie! Oh, and one more thing, there's a good chance my treasonous opinions might get me kicked out of Pennsylvania. Mom, Dad, if you're reading this, have the spare room ready. I might need it!
—Melanie Adamczyk
Mountain Top, Pennsylvania
Power of Wind
I feel compelled to weigh in on Maine's controversy over wind power, the subject of your March feature package, and my advice to you is: Quit whining. You guys, at least, still have your mountains! Unlike here in Virginia and West Virginia where our beautiful, scenic mountains are being systematically obliterated, our rivers and streams filled and/or polluted until there is no longer any life, all for the coal you think you need to power all your electronic gadgets. There is only one answer to this energy problem and that is conservation! This old earth of ours provides enough for our needs but not for our greed. We all need to reconsider our lifestyles in order to not put further strain on our rapidly depleting natural resources so that no one has to be inconvenienced by wind generators and no more mountains sacrificed.
—Martha H. Cempe
Raphine, Virginia


text:
St. Joseph Hosts Events
Weatherford Curling Classic
Broomball Tournament
This Week, Today: Mandela tributes & Alice Munro's Nobel
Stephen Harper departs for Mandela memorial service
Reaching out to Nova Scotia's homeless
Business Forecast: Job numbers show U.S. economy recovering
Please Wait A Moment.
The email and/or password you have provided is not recognized. Please verify your entry and try again. To register please close this window and click "Register" on the top right of the site.
Remember Me
Lost your password?


text:
Advanced Search or
Home > Conferences and Events > Webcasts > Webcasts
Now Offered at NO CHARGE!
Save time and money on travel by attending these highly focused events from your own office!
Listen to audio over your phone or on your computer speakers, and view presentations on the web. Participants are encouraged to submit live questions via the webcast software during the webcast. Most webcasts are two hours long and include detailed information from case studies.
Professional Development Hours (PDHs) may be earned for participating in a webcast. Please note: Webcast participants are responsible for exploring their state requirements to have their Educational Credits approved for credit.
Please email email@example.com with any webcast related questions.
Webcast Sponsorship Opportunities
Perspectives, Tips, and Lessons Learned from the Successful and Innovative P3 Military Housing Privatization Initiative 2013-12-10
Climate Information for Managing Risks in Water Resources Series 2013-12-12
A Great Utility Operation Isn't a MISSION: IMPOSSIBLE 2014-01-15


text:
Stores »
Transformers! TRANSFORM! mp3 player and dope ass transformer dude is included! Great gift!
It would be so hilarious to walk into someone office and get hit with a rocket from their desktop rocket launcher. I wold not be mad because I'd be laughing too hard at the whole scenario. Very awesome invention.
I want this one. I like TV, especially the news.....