Nahuel Bergamo Nahumancer

## rom_suffix_codes.md

      
              1 file
            
          
              6 forks
            
          
              4 comments
            
          
              116 stars
            
          
                ramiabraham
                / rom_suffix_codes.md
            
            
              Last active
              April 27, 2024 13:28
            
              
                Video game rom suffix codes (decoded)
              
          
Video game rom codes


You wouldn't download a car...


Primary rom codes

Probably what you're looking for

[a] Alternate (alternate version of the game, usually trying a different output method)
[p] Pirate


## getDependentPicklists.cls (2017 approach)
/*
* Apex doesn't expose dependent picklist info directly, but it's possible to expose.
* Approach:
*  * Schema.PicklistEntry doesn't expose validFor tokens, but they are there, and can be accessed by serializing to JSON
*    (and then for convenience, deserializing back into an Apex POJO)
*  * validFor tokens are converted from base64 representations (e.g. gAAA) to binary (100000000000000000000)
*    each character corresponds to 6 bits, determined by normal base64 encoding rules.
*  * The binary bits correspond to controlling values that are active - e.g. in the example above, this dependent option
*    is available for the first controlling field only.
*

## Mimic SQL select * statement in SOQL using Apex
/*
* @description: A code snippet that mimics the popular Select * SQL syntax in force.com's Apex language.
*/

// Initialize setup variables
String objectName = 'Contact';  // modify as needed
String query = 'SELECT';
Map<String, Schema.SObjectField> objectFields = Schema.getGlobalDescribe().get(objectName).getDescribe().fields.getMap();

// Grab the fields from the describe method and append them to the queryString one by one.
	/*
	* Apex doesn't expose dependent picklist info directly, but it's possible to expose.
	* Approach:
	* * Schema.PicklistEntry doesn't expose validFor tokens, but they are there, and can be accessed by serializing to JSON
	* (and then for convenience, deserializing back into an Apex POJO)
	* * validFor tokens are converted from base64 representations (e.g. gAAA) to binary (100000000000000000000)
	* each character corresponds to 6 bits, determined by normal base64 encoding rules.
	* * The binary bits correspond to controlling values that are active - e.g. in the example above, this dependent option
	* is available for the first controlling field only.
	*
	/*
	* @description: A code snippet that mimics the popular Select * SQL syntax in force.com's Apex language.
	*/

	// Initialize setup variables
	String objectName = 'Contact'; // modify as needed
	String query = 'SELECT';
	Map<String, Schema.SObjectField> objectFields = Schema.getGlobalDescribe().get(objectName).getDescribe().fields.getMap();

	// Grab the fields from the describe method and append them to the queryString one by one.