Skip to content

Instantly share code, notes, and snippets.

@roskakori
Last active August 29, 2015 14:10
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save roskakori/b0a3d87b5cedb673d420 to your computer and use it in GitHub Desktop.
Save roskakori/b0a3d87b5cedb673d420 to your computer and use it in GitHub Desktop.
Notes for HTLWRN team on improving cutplace
Notes for cutplace
------------------
0.9.0, week 2015/xxx
* Thomas: explain test_sql._assert_is_valid_sqlite_statement
0.9.0, week 2015/13
* Thomas: test that field names with non alphanumeric/_ are rejected
* htlwrn: continue SQL
* Heubi: clearify suggested acceptance form:
- Zeitraum: 01.09.2014 - 16.04.2015
- Aufgaben: Ticketliste
- Feedback zur Arbeit: arbeitsweise; wie eingebracht, Kommunikation, Umgangsformen, vorhandesnes technisches Know, Lernwilligkeit, Lernfähigkeit, Selbstorganisation, Prozess?; Werkzeuge, Versionierung, Tickets und Meilensteine
- Abnahmenbestätigung
0.9.0, week 2015/12
* htlwrn: continue SQL
* htlwrn: implement tests for sqllite
* Thomas: design concept for optional tests for other data bases
* Heubi: clearify acceptance form
* Jakok: fix --gui under Python 2.
* Thomas: make CID-PATH optional if --gui is specified
0.8.5, week 2015/10
* Patrick: continue SQL
* Jakob: improve gui
* Heubi:
* improve coverage for fields and ranges
* support sql
0.8.4 week 2015/9
* Thomas: cleanup decimal property place holder
- make internal
- derive 19.12 from MAX_DECIMAL_TEXT
* Thomas: add documentation for decimal range
* Jakob: improve gui
* Format buttons: CID: ____________________ [Chose...]
* Relabel button "check" to "validate"
* Cleanup: global val, w, root --> global necessary? unused variables?
* Heubi: improve coverage for fields and ranges
* Heubi: ponder on how to add precision and scale to DecimalFieldFormat to derive SQL data type.
--> result: use precesion and scale linke in SQL internally;
user specified ranges with specific values and does not have to know about this
* patrick:
* Move SQL tests from test_fields and test_interface to test_sql.
* Move methods to build SQL code from interface.Cid to factory functions in module sql.
--> cleaner code with better separation of converns
0.8.x week 2015/7
* htlwrn: use six.text_type instead of str
* htlwrn: ant flake8 detects errors but does not show them.
Workaround:
pip install -r requirements.txt
pip install -r requirements-dev.txt
Then you can check manually:
tox -e flake8
* htlwrn: for functions that return the result of a variable, use "result" as the name of the variable
0.8.x sprint week 2015/6
* Jakob:
* fix test cases in test_fields for Integer
* simplyfy IntegerFieldFormat.__init__
* try _tools.tokenize_without_space for Range
* Patrick:
* as_sql_create_table
* use sqlite for test cases
* move tests for sql to new module test_sql
* cleaned sql: rename db to sql_dialect
* cleanup validation of db in as_sql:
_VALID_SQL_DIALECTS = set([MSSQL, ...)
assert sql_dialect in _VALID_SQL_DIALECTS, 'sql_dialect=%r' % sql_dialect
* cleanup DateTimeFieldFormat.as_sql
has_time = any((format_key in self.human_readable_format()) for format_key in ('hh', 'mm', 'ss'))
has_date = any(... ('DD', 'MM', 'YY'))
* Heubi:
* continue with DecimalRange
* cleanup rendundant test cases
* Example for (sadly broken) regex to validate decimal with rule "1000.000...2000":
decimal_regex = re.compile(r'^\d{1-4}\.\d{1-3}$') # in init()
decimal_regex.match('1234.334') # in loop
* Thomas:
* clean up test_fields
* talk about test cases
* Patrick: move constants for integer ranges and DEFAULT_RANGE to module ranges
* Patrick: Implement prototype of SQL builder:
def create_table_statement(cid): ... --> str
def unload_statement(cid): ... --> str
def load_statement(cid): ... --> str
--> postponed until as_sql_create_table is mostly finished
0.8.3 sprint week 2015/4
* Heubi: state on semi complete code for DecimalField and DecimalRange?
0.8.2 sprint week 2015/03
* htlwrn: fyi:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment