persevere-framework - Project Hosting on Google Code

Yesterday 27 hours ago r656 (authenticatedUser -> remoteUser additional help for JsonQuer...) committed by kriszyp - authenticatedUser -> remoteUser additional help for JsonQuery with full-text Fixed sorting in json-query module authenticatedUser -> remoteUser additional help for JsonQuery with full-text Fixed sorting in json-query module 40 hours ago r655 (Fixes some issues with sorting where some objects have restr...) committed by kriszyp - Fixes some issues with sorting where some objects have restricted access Fixes some issues with sorting where some objects have restricted access Last 7 days Nov 09, 2009 r654 (Removes errant import) committed by kriszyp - Removes errant import Removes errant import Nov 09, 2009 r653 (Fixes doing data manipulation SQL queries) committed by kriszyp - Fixes doing data manipulation SQL queries Fixes doing data manipulation SQL queries Nov 09, 2009 r652 (persistence -> persisted) committed by kriszyp - persistence -> persisted persistence -> persisted Nov 09, 2009 r651 (Refactoring class creation Fixed transaction committing in f...) committed by kriszyp - Refactoring class creation Fixed transaction committing in full text env -> request in a number of places Refactoring class creation Fixed transaction committing in full text env -> request in a number of places Nov 06, 2009 r650 (Renamed full text module Fixed date handling with lucene) committed by kriszyp - Renamed full text module Fixed date handling with lucene Renamed full text module Fixed date handling with lucene Last 30 days Nov 04, 2009 issue 254 ("%23" (encoded #) for some reason is converted to "." in the...) commented on by d...@deanlandolt.com - Stupid google won'tl et me reopen. But in any event... The problem isn't actually fixed -- "%23" now comes in as "param0", a second %23 is param1, etc. Theoretically I could replace(/param\d/g, "#") but this would be a pretty bad hack. Stupid google won'tl et me reopen. But in any event... The problem isn't actually fixed -- "%23" now comes in as "param0", a second %23 is param1, etc. Theoretically I could replace(/param\d/g, "#") but this would be a pretty bad hack. Nov 04, 2009 issue 256 (Class ids with slashes should be broken aparet and layered i...) commented on by d...@deanlandolt.com - I found a way to do this in js by wrapping Class. It's generalizable into a customizable package model -- if anyone's interested I can add more information. I found a way to do this in js by wrapping Class. It's generalizable into a customizable package model -- if anyone's interested I can add more information. Nov 02, 2009 r649 (Determine the file path correctly inside of contexts) committed by kriszyp - Determine the file path correctly inside of contexts Determine the file path correctly inside of contexts Nov 02, 2009 r648 (Some logging debugging) committed by kriszyp - Some logging debugging Some logging debugging Nov 02, 2009 r647 (Added support for using settings for mail configuration Defa...) committed by kriszyp - Added support for using settings for mail configuration Defaults to WEB-INF/jslib for module directory if none specified Added support for using settings for mail configuration Defaults to WEB-INF/jslib for module directory if none specified Nov 02, 2009 issue 257 (ID sort order AND ID fully qualified behavior) commented on by beau.croteau - Expected Output response is in the 'additional information' section. Expected Output response is in the 'additional information' section. Nov 02, 2009 issue 257 (ID sort order AND ID fully qualified behavior) reported by beau.croteau - What steps will reproduce the problem? 1. Create class 'example_simple' 2. Add 10 objects to the class with {name:'A...J'} 3. Attempt to filter and sort: http://localhost:8080/example_simple%5B?name=%27%27][/id] What is the expected output? What do you see instead? [{id:1, id:2, id:3...}] Also, flip flops between fully qualified ID and int-only ID for specific queries. What version of the product are you using? On what operating system? R605 from Source and RC 2. Please provide any additional information below. You'll get something like the default back: http://localhost:8080/example_simple {}&&[ {"id":"example_simple/1", "name":"a" }, {"id":"example_simple/2", "name":"b" } ... But when you sort by id (it drops the 'example_simple' prefix) http://localhost:8080/example_simple%5B/id%5D {}&&[ {"id":"1", "name":"a" }, {"id":"2", "name":"b" } ... And worse filter then sort (back to what look like ints, but they're really sorted strings): http://localhost:8080/example_simple%5B?name=%27%27][/id] {}&&[ {"id":"1", "name":"a" }, {"id":"10", "name":"E" } What steps will reproduce the problem? 1. Create class 'example_simple' 2. Add 10 objects to the class with {name:'A...J'} 3. Attempt to filter and sort: http://localhost:8080/example_simple%5B?name=%27%27][/id] What is the expected output? What do you see instead? [{id:1, id:2, id:3...}] Also, flip flops between fully qualified ID and int-only ID for specific queries. What version of the product are you using? On what operating system? R605 from Source and RC 2. Please provide any additional information below. You'll get something like the default back: http://localhost:8080/example_simple {}&&[ {"id":"example_simple/1", "name":"a" }, {"id":"example_simple/2", "name":"b" } ... But when you sort by id (it drops the 'example_simple' prefix) http://localhost:8080/example_simple%5B/id%5D {}&&[ {"id":"1", "name":"a" }, {"id":"2", "name":"b" } ... And worse filter then sort (back to what look like ints, but they're really sorted strings): http://localhost:8080/example_simple%5B?name=%27%27][/id] {}&&[ {"id":"1", "name":"a" }, {"id":"10", "name":"E" } Oct 30, 2009 issue 256 (Class ids with slashes should be broken aparet and layered i...) reported by d...@deanlandolt.com - Here's a patch to add . This could probably be a little nicer, but it gets the job done. I've tested and all is well but I'll create some core tests to test this and other slash-based package functionality and throw another patch over the fence. Here's a patch to add . This could probably be a little nicer, but it gets the job done. I've tested and all is well but I'll create some core tests to test this and other slash-based package functionality and throw another patch over the fence. Oct 30, 2009 r646 (Refactored lazy arrays to use some method instead of forEach...) committed by kriszyp - Refactored lazy arrays to use some method instead of forEach for more efficient exits Refactored lazy arrays to use some method instead of forEach for more efficient exits Oct 30, 2009 issue 254 ("%23" (encoded #) for some reason is converted to "." in the...) Status changed by kriszyp - Status: Fixed Status: Fixed Oct 30, 2009 r645 (Fixes handling of # in some ids) committed by kriszyp - Fixes handling of # in some ids Fixes handling of # in some ids Oct 30, 2009 issue 255 (content negotiation broken in 1.0 tip) Status changed by kriszyp - Status: Fixed Status: Fixed Oct 30, 2009 r644 (Fixed Accept header handler) committed by kriszyp - Fixed Accept header handler Fixed Accept header handler Oct 30, 2009 r643 (Fixed an unnecessary import Turn on idle checking of connect...) committed by kriszyp - Fixed an unnecessary import Turn on idle checking of connections Fixed an unnecessary import Turn on idle checking of connections Oct 29, 2009 r642 (Refactoring for separate JSGI apps) committed by kriszyp - Refactoring for separate JSGI apps Refactoring for separate JSGI apps Oct 29, 2009 issue 255 (content negotiation broken in 1.0 tip) reported by d...@deanlandolt.com - Negotiation is broken in 1.0 tip -- no matter what the Accept, the resolved representation always goes to the highest quality (or, if no quality >= 0.9, application/javascript). Negotiation is broken in 1.0 tip -- no matter what the Accept, the resolved representation always goes to the highest quality (or, if no quality >= 0.9, application/javascript). Oct 29, 2009 issue 254 ("%23" (encoded #) for some reason is converted to "." in the...) reported by d...@deanlandolt.com - GET /SomeClass/1.someMethod("a%23b") ...should result in arg1 to someMethod being "a#b", right? But what's coming in instead is "a.b" GET /SomeClass/1.someMethod("a%23b") ...should result in arg1 to someMethod being "a#b", right? But what's coming in instead is "a.b" Oct 29, 2009 issue 253 (accept parsing fails with wildcards) reported by d...@deanlandolt.com - Accept: text/html works fine, but Accept: /html or text/ breaks. Accept: / always serves application/javascript Accept: text/html works fine, but Accept: /html or text/ breaks. Accept: / always serves application/javascript Oct 28, 2009 r641 (Various updates to Pintura, fixes some object creation issue...) committed by kriszyp - Various updates to Pintura, fixes some object creation issues Various updates to Pintura, fixes some object creation issues Oct 28, 2009 r640 (Include Accept header in login request) committed by kriszyp - Include Accept header in login request Include Accept header in login request Oct 27, 2009 r639 (Added ability to specify with a function whether or not to s...) committed by kriszyp - Added ability to specify with a function whether or not to serialize a particular property Added ability to specify with a function whether or not to serialize a particular property Oct 27, 2009 r638 (Fixes indexing issue with large commits Makes JSON parse err...) committed by kriszyp - Fixes indexing issue with large commits Makes JSON parse errors catcheable Fixes indexing issue with large commits Makes JSON parse errors catcheable Oct 27, 2009 r637 ([No log message]) committed by kriszyp - [No log message] [No log message] Oct 26, 2009 r636 (Various updates) committed by kriszyp - Various updates Various updates Oct 26, 2009 r635 (Updates to faceting) committed by kriszyp - Updates to faceting Updates to faceting Oct 23, 2009 r634 (Fixes check for up directory reference) committed by kriszyp - Fixes check for up directory reference Fixes check for up directory reference Oct 23, 2009 r633 (Updates to authorization to use more of an object capability...) committed by kriszyp - Updates to authorization to use more of an object capability model approach Updates to authorization to use more of an object capability model approach Oct 22, 2009 r632 (Fix security to make it usable) committed by kriszyp - Fix security to make it usable Fix security to make it usable Oct 22, 2009 r631 (Adding more missing files) committed by kriszyp - Adding more missing files Adding more missing files Oct 22, 2009 r630 (Checkin files I forgot to add) committed by kriszyp - Checkin files I forgot to add Checkin files I forgot to add Oct 22, 2009 r629 (Updates for authentication/authorization) committed by kriszyp - Updates for authentication/authorization Updates for authentication/authorization Oct 22, 2009 r628 (Updates to SQLStore for improved SQLLite and better connecti...) committed by kriszyp - Updates to SQLStore for improved SQLLite and better connection management Updates to SQLStore for improved SQLLite and better connection management Oct 21, 2009 r627 (Read accept header from env) committed by kriszyp - Read accept header from env Read accept header from env Oct 20, 2009 r626 (Added JSON/JS serialization for SQLStore Aborts transactions...) committed by kriszyp - Added JSON/JS serialization for SQLStore Aborts transactions properly when an error occurs Added JSON/JS serialization for SQLStore Aborts transactions properly when an error occurs Oct 20, 2009 r625 (Add support for serializing dates in SQLite) committed by kriszyp - Add support for serializing dates in SQLite Add support for serializing dates in SQLite Oct 20, 2009 r624 (Create lucene store files if they don't exist better cross-d...) committed by kriszyp - Create lucene store files if they don't exist better cross-db test for a table Create lucene store files if they don't exist better cross-db test for a table Oct 20, 2009 r623 (Include org/jackjs in the build) committed by kriszyp - Include org/jackjs in the build Include org/jackjs in the build Oct 20, 2009 r622 (Continued updates to make persvr run on jack) committed by kriszyp - Continued updates to make persvr run on jack Continued updates to make persvr run on jack Oct 16, 2009 r621 (Fix of issue with relative paths when classes have slashes i...) committed by kriszyp - Fix of issue with relative paths when classes have slashes in their names Fix of issue with relative paths when classes have slashes in their names Oct 14, 2009 r620 (Handle date conversion) committed by kriszyp - Handle date conversion Handle date conversion Oct 14, 2009 r619 (Added some missing classes) committed by kriszyp - Added some missing classes Added some missing classes Oct 14, 2009 r618 (Imported Narwhal (no way to do svn:externals to a git repo) ...) committed by kriszyp - Imported Narwhal (no way to do svn:externals to a git repo) Switching to using Jack for request handling Imported Narwhal (no way to do svn:externals to a git repo) Switching to using Jack for request handling Oct 14, 2009 r617 (Creating a 2.0 branch for some of the dev work not ready for...) committed by kriszyp - Creating a 2.0 branch for some of the dev work not ready for trunk. Creating a 2.0 branch for some of the dev work not ready for trunk.

issue 257 (ID sort order AND ID fully qualified behavior) reported by beau.croteau - What steps will reproduce the problem? 1. Create class 'example_simple' 2. Add 10 objects to the class with {name:'A...J'} 3. Attempt to filter and sort: http://localhost:8080/example_simple%5B?name=%27*%27][/id] What is the expected output? What do you see instead? [{id:1, id:2, id:3...}] Also, flip flops between fully qualified ID and int-only ID for specific queries. What version of the product are you using? On what operating system? R605 from Source and RC 2. Please provide any additional information below. You'll get something like the default back: http://localhost:8080/example_simple {}&&[ {"id":"example_simple/1", "name":"a" }, {"id":"example_simple/2", "name":"b" } ... But when you sort by id (it drops the 'example_simple' prefix) http://localhost:8080/example_simple%5B/id%5D {}&&[ {"id":"1", "name":"a" }, {"id":"2", "name":"b" } ... And worse filter then sort (back to what look like ints, but they're really sorted strings): http://localhost:8080/example_simple%5B?name=%27*%27][/id] {}&&[ {"id":"1", "name":"a" }, {"id":"10", "name":"E" }

What steps will reproduce the problem? 1. Create class 'example_simple' 2. Add 10 objects to the class with {name:'A...J'} 3. Attempt to filter and sort: http://localhost:8080/example_simple%5B?name=%27*%27][/id] What is the expected output? What do you see instead? [{id:1, id:2, id:3...}] Also, flip flops between fully qualified ID and int-only ID for specific queries. What version of the product are you using? On what operating system? R605 from Source and RC 2. Please provide any additional information below. You'll get something like the default back: http://localhost:8080/example_simple {}&&[ {"id":"example_simple/1", "name":"a" }, {"id":"example_simple/2", "name":"b" } ... But when you sort by id (it drops the 'example_simple' prefix) http://localhost:8080/example_simple%5B/id%5D {}&&[ {"id":"1", "name":"a" }, {"id":"2", "name":"b" } ... And worse filter then sort (back to what look like ints, but they're really sorted strings): http://localhost:8080/example_simple%5B?name=%27*%27][/id] {}&&[ {"id":"1", "name":"a" }, {"id":"10", "name":"E" }

Yesterday

Last 7 days

Last 30 days