This commit is contained in:
@@ -31,6 +31,8 @@ todo: AyaFormFieldDefinitions looking a little suspect now as it gets huge.
|
|||||||
should it really cache all of them all the time?
|
should it really cache all of them all the time?
|
||||||
would it be faster / better for memory to return as requested dynamically (switch?)
|
would it be faster / better for memory to return as requested dynamically (switch?)
|
||||||
|
|
||||||
|
todo: now that have name fetcher in stored procedure can the c# version be ditched for more efficient fetches for stuff that calls it?
|
||||||
|
|
||||||
todo: Help for list / editor form combo should be combined into list help alone
|
todo: Help for list / editor form combo should be combined into list help alone
|
||||||
no reason to have separate
|
no reason to have separate
|
||||||
grid part can just say what's unique and link to standard grid help
|
grid part can just say what's unique and link to standard grid help
|
||||||
@@ -46,39 +48,17 @@ TODO: //MIGRATE_OUTSTANDING comment tag
|
|||||||
The tag will contain the description for each
|
The tag will contain the description for each
|
||||||
............................................................
|
............................................................
|
||||||
|
|
||||||
****
|
|
||||||
CREATE OR REPLACE FUNCTION PUBLIC.AYGETNAME(IN AYOBJECTID bigint, IN AYOBJECTTYPE integer) RETURNS text AS $BODY$
|
|
||||||
DECLARE
|
|
||||||
aytable TEXT DEFAULT '';
|
|
||||||
aynamecolumn TEXT DEFAULT 'name';
|
|
||||||
returnstr TEXT DEFAULT '';
|
|
||||||
BEGIN
|
|
||||||
-- Object type to table name
|
|
||||||
case ayobjecttype
|
|
||||||
when 8 then
|
|
||||||
aytable = 'acustomer';
|
|
||||||
when 2 then
|
|
||||||
aytable = 'awidget';
|
|
||||||
when 33 then
|
|
||||||
aytable = 'avendor';
|
|
||||||
else
|
|
||||||
-- unknown or not supported just return default string
|
|
||||||
RETURN '-';
|
|
||||||
end case;
|
|
||||||
EXECUTE format('SELECT %I FROM %I WHERE id = %L', aynamecolumn, aytable, ayobjectid) INTO returnstr;
|
|
||||||
RETURN returnstr;
|
|
||||||
END;
|
|
||||||
$BODY$ LANGUAGE PLPGSQL STABLE
|
|
||||||
****
|
|
||||||
|
|
||||||
currently doing: Reminder - was regular non followup schedulemarker, Review - was follow up schedule marker
|
|
||||||
|
|
||||||
|
|
||||||
Going to need a bunch of translation keys for both objects
|
|
||||||
Front end may be a bit more time consuming on this one so do the v8 migrate maybe first so have realistic data to work with
|
|
||||||
|
|
||||||
|
|
||||||
|
currently doing:
|
||||||
|
Reminder - was regular non followup schedulemarker, Review - was follow up schedule marker
|
||||||
|
Front end may be a bit more time consuming on this one so do the v8 migrate maybe first so have realistic data to work with
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
EACH OBJECT DEV CYCLE:
|
EACH OBJECT DEV CYCLE:
|
||||||
FIRST
|
FIRST
|
||||||
Check cases, make sure not changing the object fundamentally, many v7 objects are going to change for cases (particularly inventory related)
|
Check cases, make sure not changing the object fundamentally, many v7 objects are going to change for cases (particularly inventory related)
|
||||||
|
|||||||
Reference in New Issue
Block a user